Build Systems Rework

[hoijui]

As i understand it, this is how buildsystems work:

• configure: needed tools and libraries and sources are inspected and so on, you know.
• make: builds binaries in the build-dir. nothing changes in the source tree (except if it is equal with the build dir). nothing changes in the install dir(s). after this step, the build-dir can be used to test the end product. eg:
  cd mySpringBuildDir
  ./spring.exe
• make install: (= make + install) just copies the parts needed for operation to the install dir(s) (eg. spring.exe -> yes, Util.o -> no).

i think it would be nice if we could have it like this. and i am willing to do my part (take configurable scons build dir and scons streflop build as the beginning).

[Auswaschbar]

I don't understand this post. Isn't it like this already?

[hoijui]

no, it is not. spring(.exe) and unitsync.dll do not ever end up in the build dir for example, but always under game/the install dir, and that during the make (without install) step. some things always get built in the source tree (eg. precompiled headers).

the installer only works if you have things in repoRoot/game.

lots of the new AI Interface (java stuff) is built in the source tree...
woops :D

i do not remember anything else right now, but there could be more.

[lurker]

It goes into game with scons, but every time I have used make without install it has gone into build/rts.