Code::Blocks Forums

User forums => Using Code::Blocks => Topic started by: Mazze on October 16, 2009, 11:54:27 am

Title: Search path in custom makefile when cross-compiling
Post by: Mazze on October 16, 2009, 11:54:27 am

I want to cross-compile with a custom makefile.

I have the lines
CC=i386-aros-gcc
LD=i386-aros-gcc
in the makefile.

This fails because c::b ignores the Linux search path. Compiling works when I write the full path in the CC variable.
But I don't want to have a path which is only valid on my machine in the makefile.

So how can I tell c::b about the path of the required tools?

Title: Re: Search path in custom makefile when cross-compiling
Post by: stahta01 on October 17, 2009, 04:01:42 am

Does it work right when using the make command (outside of Code::Blocks)?
If not, fix it for make then try again with Code::Blocks.

Edit: Try doing full compiler logging and see if that gives info. Not sure how it works with custom makefile.
http://wiki.codeblocks.org/index.php?title=FAQ#Q:_How_do_I_troubleshoot_an_compiler_problem.3F

Tim S.

Title: Re: Search path in custom makefile when cross-compiling
Post by: Mazze on October 17, 2009, 09:40:14 am

Thanks. It's working now. I defined a cross-compiler like explained here:
http://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers

Although I'm using a custom makefile c::b is using the path from the cross-compiler setup.

Title: Re: Search path in custom makefile when cross-compiling
Post by: Mazze on October 17, 2009, 11:14:09 am

Stop. I drew wrong conclusions.

What made it working was starting c::b from the console instead of Gnome menu.

Title: Re: Search path in custom makefile when cross-compiling
Post by: Jenna on October 17, 2009, 12:41:01 pm

That means gnome does not pass your environment to C::B, most likely the (some) startup-scripts are only used in login-shells.

So no C::B issue, but a gnome (configuration?) problem.

Title: Re: Search path in custom makefile when cross-compiling
Post by: Mazze on October 17, 2009, 02:17:13 pm

> So no C::B issue, but a gnome (configuration?) problem

Yes.
I guess that gnome doesn't use a path which I've set in my .bashrc.