the old linker-version (in PB V3.81) doesn't support more than one res file. Has this behaviour changed in the beta (and so in the next releases)?
or exist a 100% compatible lcclnk.exe with multi resource support?
Would be nice to know for jaPBe. So i don't must use ResHacker for including resources...
GPI
p.s.: i know, there is a other thread about lcclnk. But i think my question is a little bit diffrent...
lcclnk.exe in the compiler directory [beta]
-
RJP Computing
- Enthusiast

- Posts: 202
- Joined: Sun Apr 27, 2003 4:44 am
- Location: Michigan, USA
- Contact:
Found out, that GoRC can "compile" RC and Res to Obj. And the linker doesn't have any problems with many .obj-files....
And the moment, japbe creates "_japbe_<nb>.obj"-files in the compiler-director and the call the linker manual (with the fake-linker and a patched pbcompiler.exe, which start fcclnk.exe instead of lcclnk.exe).
My question is: Which name for jaPBe-Generated object-files are secure, so i don't have any conflicts with the pb-compiler ?
Edit: btw: a optional parameter of the compiler/IDE to add many costum .obj would be nice.
And the moment, japbe creates "_japbe_<nb>.obj"-files in the compiler-director and the call the linker manual (with the fake-linker and a patched pbcompiler.exe, which start fcclnk.exe instead of lcclnk.exe).
My question is: Which name for jaPBe-Generated object-files are secure, so i don't have any conflicts with the pb-compiler ?
Edit: btw: a optional parameter of the compiler/IDE to add many costum .obj would be nice.
Lcclnk DOES support more than one .RES or .LIB file. It's simply the PBCompiler that passes just one argument to Lcclnk. In the meanwhile I've successfully modified the PBCompiler so it passes another .RES file as argument to linker and it works fine. Of course, this is just for personal use as I really needed this feature because I had hundreds of files to include as RC_DATA and it taked 1 hour to manually include them with ResHacker.
No, it doesn't. I test it with the linker in the compilers\ directory.Seldon wrote:Lcclnk DOES support more than one .RES or .LIB file. It's simply the PBCompiler that passes just one argument to Lcclnk.
My methode was simpler. I change the compiler so, that he start fcclnk.exe and not lcclnk.exe. So i can get all parameters, which PBCompiler sends to the linker and modify it.In the meanwhile I've successfully modified the PBCompiler so it passes another .RES file as argument to linker and it works fine. Of course, this is just for personal use as I really needed this feature because I had hundreds of files to include as RC_DATA and it taked 1 hour to manually include them with ResHacker.

