User forums > Help

Compiler Installation directory as C::B Variable

<< < (2/2)

christobal:

--- Quote from: oBFusCATed on December 01, 2009, 04:02:05 pm ---I've expected the answer to be weird, but that weird  :lol:  :shock:

--- End quote ---

My build target is a static library. Some of the object files are generated from the sources and some are copied from another library. I wouldn't say that it's weird... But if you know a better way to move object files from one lib to another, please tell me  :wink:.

stahta01:
I suggest using an environmental/system variable if it is just Windows; not sure if this would work with Linux.

Tim S.

MortenMacFly:
Global variables is what you are looking for. Once defined if you open the project file on another computer C::B will query (once) for the location of the compiler. This way you can assure that the setup is correct on the target platform. This works cross-platform, of course.

Same applies to e.g. libraries like boost. Just define a global variable and it'll be qeried on another compuert (even another account) if not defined there.

MortenMacFly:

--- Quote from: christobal on December 01, 2009, 04:27:06 pm ---My build target is a static library. Some of the object files are generated from the sources and some are copied from another library. I wouldn't say that it's weird... But if you know a better way to move object files from one lib to another, please tell me  :wink:.

--- End quote ---
If the object files from the other library are propriatary you won't have any other chance most likely. However, if you have access to the sources I'd rather compile them (another time) to avoid e.g. ABI incompatibilities. It always shiffers me if I have to use object files I can't compile myself. I even had to abandon a whole project back in the days because the provided object files were not compatible with new kernel versions and were not updated anymore. When we bought the 3rd party stuff (for tons of money, of course) it was said "life-time support".... Tssss. Life-time assholes probably, but that's it. You see: This can be mission-critical.

christobal:

--- Quote from: MortenMacFly on December 01, 2009, 08:16:24 pm ---Global variables is what you are looking for. Once defined if you open the project file on another computer C::B will query (once) for the location of the compiler. This way you can assure that the setup is correct on the target platform. This works cross-platform, of course.

Same applies to e.g. libraries like boost. Just define a global variable and it'll be qeried on another compuert (even another account) if not defined there.


--- End quote ---

The Global Variables are a good solution. I will use them, thanks!

Navigation

[0] Message Index

[*] Previous page