Author Topic: Resources problem (windres.exe >> MinGW) Typo?  (Read 6794 times)

Anonymous

  • Guest
Resources problem (windres.exe >> MinGW) Typo?
« on: April 29, 2005, 12:06:36 am »
When compiling a project with a resource script (.rc) using MinGW i get this:

Quote
windres.exe: invalid option -- J


The command line is this:

Quote
windres.exe -i code\resource.rc -J rc -o code\.objs\code\resource.res -O coff


Shouldn't it be like this:

Quote
windres.exe -i code\resource.rc -I rc -o code\.objs\code\resource.res -O coff


* Notice the -I instead of -J! *

If that's the problem then how can I replace the -J that goes into the command line (in CB)?

Thanks! (Hope I didn't post a complete bullshit, I'm not sure if that's the problem)

Oh... almost forgot... beta7!

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4291
    • Code::Blocks IDE
Resources problem (windres.exe >> MinGW) Typo?
« Reply #1 on: April 29, 2005, 10:14:55 am »
Nobody is using the search?
Here...

Yiannis.
Be patient!
This bug will be fixed soon...

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
Resources problem (windres.exe >> MinGW) Typo?
« Reply #2 on: April 29, 2005, 09:30:29 pm »
Oh, that little rectangle on the top right? No, I guess not. ^^;

Anonymous

  • Guest
Resources problem (windres.exe >> MinGW) Typo?
« Reply #3 on: April 29, 2005, 10:27:05 pm »
I'm so so sorry for not using the search (I didn't know this forum had it). Before I post I took a look at the 1st and 2nd pages of the forum but I didn't see the search box up there.

Anyway, that worked! It's fixed now, thanks a lot...

Anonymous

  • Guest
Resources problem (windres.exe >> MinGW) Typo?
« Reply #4 on: April 29, 2005, 11:07:33 pm »
Oh, one more thing, when I try to debug (run to cursor) the project I get this:

Quote

Selecting target: mingw(debugging)
Compiling: done
Starting debugger: done
Adding source dir: C:/Programming/Editor/
No source file named code\main.cpp.
error


It seems gdb can't find the source file (all of them are located in 'code' dir inside them project's dir. Does anyone know how can I make it work?  (I used the search feature now ;) )

Sorry for being such a pain in the *ss

Anonymous

  • Guest
Resources problem (windres.exe >> MinGW) Typo?
« Reply #5 on: May 07, 2005, 06:34:59 pm »
Plz, can anyone help, I've tried lots of things and it still doesn't works...

The problem seems to be that GDB isn't understanding "code\main.cpp" as 'main.cpp' in the 'code' folder, it's understanding as a file named "code\main.cpp" (just a guess though)

I've copied the project and put all the sources in the same folder as the project and it works, but I don't like keeping it that way because it's very messy in a 50+ source files project...

Can anyone help me?

Anonymous

  • Guest
Resources problem (windres.exe >> MinGW) Typo?
« Reply #6 on: May 07, 2005, 06:35:43 pm »
Oh, and I've tried the search feature...

Offline David Perfors

  • Developer
  • Lives here!
  • *****
  • Posts: 560
Resources problem (windres.exe >> MinGW) Typo?
« Reply #7 on: May 07, 2005, 07:36:03 pm »
It is very strange, but I think GDB can't handle the "\" sign. Do you have "\" somewhere in your includes? if so, try changing it to the linux style "/". That is the only thing I can think of...
OS: winXP
Compiler: mingw
IDE: Code::Blocks SVN WX: 2.8.4 Wish list: faster code completion, easier debugging, refactoring

Anonymous

  • Guest
Resources problem (windres.exe >> MinGW) Typo?
« Reply #8 on: May 08, 2005, 06:11:46 am »
That could be the reason, but the problem is that the '\' is added by CB itself and I can't find a way to bypass it (I've tried changing '\' into '/' inside the .cbp file with no success)... All my includes and etc use just the filename (they are like '#include "main.h"' no 'code\'), so I'm a bit lost...

Thanks for the reply

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
Resources problem (windres.exe >> MinGW) Typo?
« Reply #9 on: May 08, 2005, 07:35:29 am »
my solution is, until the debugger plugin is better implemented, to use the commandline gdb.

It takes a bit to get used to it, but hey, when you're trying to hunt segfaults for 2 hours, it's easier everytime :P