« previous next »
Pages: [1]   Go Down

Author Topic: library files have incorrect path name  (Read 4995 times)

jarro_2783

  • Guest
library files have incorrect path name
« on: April 20, 2006, 10:29:56 am »
When I use a make file to compile something, library files that I include are being given the wrong path name.
The linker gives an error that is something along the lines of:
c:programmingprogramsjffbzlib.a not found.
Clearly it is losing the \ somehow. Is there a way to fix this or is this a bug?
Logged

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: library files have incorrect path name
« Reply #1 on: April 20, 2006, 11:38:57 am »
It would be helpful to know what version you are actually using, as the expansion of pathnames has  at least been rewritten 3 times during the last 9 months.

Since you're talking about makefiles, however, it is probably a bug. If you are using RC2, it is a bug in RC2, and if you are using a recent build, it is a bug in your self-made makefile (since export to makefile no longer exists).
Logged
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

jarro_2783

  • Guest
Re: library files have incorrect path name
« Reply #2 on: April 20, 2006, 01:07:11 pm »
I'm using RC2. It happens when I export the makefile and then run make from the command prompt, when I compile from makefile and when I compile directly (from settings -> compiler -> other.
Logged

sethjackson

  • Guest
Re: library files have incorrect path name
« Reply #3 on: April 20, 2006, 03:22:43 pm »
Quote from: jarro_2783 on April 20, 2006, 01:07:11 pm
I'm using RC2. It happens when I export the makefile and then run make from the command prompt, when I compile from makefile and when I compile directly (from settings -> compiler -> other.

Get a nightly from here. :D RC2 is sooo old.

http://forums.codeblocks.org/index.php?board=20.0
Logged
Pages: [1]   Go Up
« previous next »