Pelles C forum

Pelles C => Bug reports => Topic started by: svobodb on March 16, 2011, 01:26:34 PM

Title: PORC invalid relative #include paths
Post by: svobodb on March 16, 2011, 01:26:34 PM

Hi, we have recently discovered invalid implementation of #pragma code_page in MSVC's RC.EXE (version 5.0 through 2010). We need a RC.EXE replacement, so I found Pelles C software. Very impressive work, I must say.

Your PORC.EXE works great for us except it handles wrong relative includes containing "..\". PORC does not take the source file location as the base in this case but either the executable's starting directory or the compiled RC file's path (I didn't check which one). I believe that the source file location (which's directory may be different when e.g. included from the compiled RC file) is correct base for that. MSVC, GCC, and Wine's wrc behave like this.

Note that the relative include paths are derived correctly when they are just plain file names without "..\".

Title: Re: PORC invalid relative #include paths
Post by: Pelle on April 17, 2011, 04:03:54 PM

Right. It looks like this "feature" has been there since the start, and this is the first complain about it. I'm guessing it's not a popular feature, so changing it should have little effect on existing files.
Sounds like a good change; should work in 6.50, RC4.