-
In our environment we support cross compilation of our code for different target platforms. E.g. it could be that we compile on a 32 bit compiler and target a 64 bit system.
For this environment we have split up the compilation of the tools that bootstrap the compilation and the compilation itself.
In other words internal build tools are first compiled manually using one set of environment...
2009-10-02 08:46:27 UTC in makepp
-
I would like to be able to treat makepp warnings as errors. The reason why is that when compiling code on multiple platforms the output files are not always the same. Eventually makepp gives warnings which should be handled. However when running makepp using automated builds these warnings can be missed.
Thus I would like to have a hard stop to ensure that it gets properly fixed.
Is this...
2009-06-22 06:47:54 UTC in makepp
-
Instead what I did was to make use of another feature like:
$(OBJECTS) : CPLATFORM += -DXF_TESTCASE
This seems to work fine for one makefile. However I am starting to believe there are bugs in makepp. Because for another makefile it only worked on the first item when I specified it as:
$(OBJECTS_A) : CPLATFORM += -DXF_TESTCASE
$(OBJECTS_B) : CPLATFORM += -DXF_TESTCASE
$(OBJECTS_C) ...
2009-05-06 06:30:02 UTC in makepp
-
I have a case where I have an executable that depends on a shared library. Thus as a dependency for the exe then there is a dependency to build the library.
Now the compilation of these are almost identical except for one define "-Dsomeflag". The rules to build both targets are placed in one common place. So if I add the "-Dsomeflag" then I will accidently make it apply...
2009-04-25 18:03:16 UTC in makepp
