BlackBox Framework Center

It is annoying that with every module added there is a change required in the file Dev/Docu/Build-Tool.odc.
This creates merge conflicts and it is easy to forget to add a new module. It is also required to make
a change if the compile order of modules changes. Another source for oversights and merge conflicts.

The solution to this problem would be to use the generic DevCompiler.CompileSubs command below:

DevCompiler.CompileSubs Com Comm Ctl Dev Form Host Obx Ole Sql Std System Text Win Xhtml

Any comments?

- Josef

Josef Templ wrote:DevCompiler.CompileSubs Com Comm Ctl Dev Form Host Obx Ole Sql Std System Text Win Xhtml

Is that list meant to be exhaustive?

Yes, this is the list of subsystems included in the standard distribution.
It compiles the same number of modules as the explicit form currently being used.

If a new subsystem is added, this list would have to be extended.
Currently it is not possible to use the wildcard version "DevCompiler.CompileSubs *" to compile
ALL subsystems because the subsystem "Script" would then also be included but it is
only compiled when building a new scripting engine (bbscript.exe).

- Josef

Josef Templ wrote:Any comments?

I suspect that most of the rest of us don't know much about the inner working of the build-tool. If you think this is a good idea, just go ahead and do it.
(Certainly tell us, in outline, what you have done.)

I have created infrastructure issue-#162 for this change.
Please see the diffs in https://redmine.blackboxframework.org/p ... 1&type=sbs.

The module ObxRatCalc is actually not changed at all but renamed.
Under Windows this is irrelevant. However, when using a case sensitive file system, e.g. with a Linux or BSD port,
it makes a difference. This has been reported by X512 in the community forum.

- Josef

Josef Templ wrote:I have created infrastructure issue-#162 for this change.
Please see the diffs in https://redmine.blackboxframework.org/p ... 1&type=sbs.

The module ObxRatCalc is actually not changed at all but renamed.
Under Windows this is irrelevant. However, when using a case sensitive file system, e.g. with a Linux or BSD port,
it makes a difference. This has been reported by X512 in the community forum.

- Josef

I've read the dif file (nice) but why is this needed? I am completely lost on what the "Build-Tool" does and is supposed to do.
-Doug

The Build-Tool contains the commands to compile and link a new BlackBox.
It is executed as the core of the automated build process by means of a tool (bbscript.exe).
bbscript.exe constitutes a scripting engine. It is an adapted version of BlackBox.exe
with very few modifications only (see subsystem Script) that opens a specified file and
executes all its commands from top to bottom.

- Josef

Josef
I assume you have just done this. There is nothing (a vote maybe) that we need to do?

Robert wrote:Josef
I assume you have just done this. There is nothing (a vote maybe) that we need to do?

Right, there are no other changes.

From my point of view, this is ready for merging to master.
There have not been any objections so far and this is a simplification
that avoids some merge conflicts in the future.

Voting does not give much sense in this case, I think.
I have done the merge.

- Josef

FYI: I had to fix another little issue in Script/Mod/Changes.
When there was no description in an issue there was a problem with generating the change log.

The diffs are https://redmine.blackboxframework.org/p ... f0270e5122.

- Josef