Tweet
Breaking up project sources
Presently, I only have PBCC. I never much cared for GUI programming, though I have done some in Python.
I have a project with a local law firm. A custom application is required because they want it to meet very exact specifications. I started with a monolithic mr.bas giving mr.exe. Both are called from Windows Scheduler and have no UI. Today it is 7 revisions later and I have monolithic mr.bas and ar.bas. They share enough code that I really need to have a third file for each to $INCLUDE.
If I were doing this in C++, I would have at least config.h, mr.cpp, ar.cpp, and common.cpp. Then I would make a Makefile to compile and link ar and mr.
Now there is talk of converting this to a service or (hopefully not) two services plus a GUI front-end. So we are still talking >= 2 executables.
PBWin8 can do the job, of course. I am just curious about its project management features. Can multiple .exe's be built at once? Is there a Make or other facility so you compile only what needs to be compiled and not recompile what has not changed?
I have a project with a local law firm. A custom application is required because they want it to meet very exact specifications. I started with a monolithic mr.bas giving mr.exe. Both are called from Windows Scheduler and have no UI. Today it is 7 revisions later and I have monolithic mr.bas and ar.bas. They share enough code that I really need to have a third file for each to $INCLUDE.
If I were doing this in C++, I would have at least config.h, mr.cpp, ar.cpp, and common.cpp. Then I would make a Makefile to compile and link ar and mr.
Now there is talk of converting this to a service or (hopefully not) two services plus a GUI front-end. So we are still talking >= 2 executables.
PBWin8 can do the job, of course. I am just curious about its project management features. Can multiple .exe's be built at once? Is there a Make or other facility so you compile only what needs to be compiled and not recompile what has not changed?
Comment