Toolchain broken after changing the Current toolchain setting

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Toolchain broken after changing the Current toolchain setting

1,008 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by laszlofabian on Thu Nov 21 14:19:04 MST 2013
Hi,

I was tweaking around, being annoyed that adding an asm module is not linking, so changed the current toolchain to Mingw GCC tried to compile, didn't work than changed it back.
The otherwise compiled project (by removing the asm function) is not compiling anymore, errors related to undefined reference to __bss_end__ and similar gcc like variables are missing. I have moved back the toolchain setting to Code red, this change seems to be broken something.

I must say beside that the include paths in Release mode are not working. I am trying to make this work, otherwise I will set-up from ground up an eclipse+gcc toolchain, this LPCXpresso IDE is more pain than gain...

LE: The issue is 100% reproducible, just make a demo LPC project for Code red tools, compile it, then change the toolchain for some gcc, try compile, fails because the gcc is not in path... than change it back, it will never compile again.

Regards,

0 Kudos
Reply
3 Replies

987 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Mon Nov 25 07:11:15 MST 2013
In a typical project, there are two build configurations - Debug and Release. These are independent of each other. If you need to add an Include path, it should be added to BOTH configurations. I suspect that you have not added correct include path for the Release build.

To select the current configuration, at the top of the dialog, there is a Configuration drop-down list. This also has an option for [All configurations].

There is lots of information on build settings in the Help (Help->Help contents).
0 Kudos
Reply

987 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by laszlofabian on Mon Nov 25 06:17:40 MST 2013
Thank you for the answer, now it makes more sense.

My general problem was/is to get used to how the IDE is managing the paths, especially the include paths.
For example if I move the build setup to Release the typedefs (uint32_t) are not available, even though I have the headers there and the project compiles for Debug mode, and the project setup has all the include paths.

The second idea was to change to the gcc toolchain, but I have the make error that gcc is not found in the Path env. variable.

I am using the latest LPCXpresso

Regards,
Laszlo
0 Kudos
Reply

987 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Fri Nov 22 00:31:23 MST 2013
When you switch toolchains, settings that are applicable to both toolchains are retained, but settings that are specific to a toolchain are lost.

The LPCXpresso tools have some specific settings (mostly on the "Target" tab of each individual tool) that are lost (as they do not apply to other toolchains) and so are being reset to default values. You need to restore those settings to be those that are appropriate for your target:
- the Architecture (Cortex-M3/M4/M0 etc)
- The C library type
- the Manage Linker script flag, or the Linker script name
- etc

But what was your original problem? Perhaps if you describe the issue you were having we can suggest how to resolve it.
0 Kudos
Reply