I've got two separate solutions in a workspace, one building at x86 (GCC x64 with -m32), the other building the same set of files at x64 (GCC).
Unfortunately because they're building the same files, Codelite believes that it can share the .o files across the two solution builds, which obviously leads to link errors. The same scenario would occur if two workspaces were using some of the same files but different compilers.
Solutions sharing build .o's within workspace
-
- CodeLite Enthusiast
- Posts: 45
- Joined: Tue Jan 28, 2014 3:03 pm
- Genuine User: Yes
- IDE Question: C++
- Contact:
- eranif
- CodeLite Plugin
- Posts: 6375
- Joined: Wed Feb 06, 2008 9:29 pm
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: Solutions sharing build .o's within workspace
So, so you have two projects, building the *exact* set of source files, one for 64 and one for 32 bits?
The proper solution is to create 2 different build configuration for one of the projects.
In the first one, use the 64 bit toolchain and in the second, use the 32 bit toolchain.
To make sure the linker does mix between the objects, make sure you put them in a different intermediate folder (project settings->general->intermediate folder)
Eran
The proper solution is to create 2 different build configuration for one of the projects.
In the first one, use the 64 bit toolchain and in the second, use the 32 bit toolchain.
To make sure the linker does mix between the objects, make sure you put them in a different intermediate folder (project settings->general->intermediate folder)
Eran
Make sure you have read the HOW TO POST thread