How can I convince build / link to link more than one compiled resource
script into one driver image? Is there a linker switch I did not find?
Everytime when I include 2 *.rc files into “sources” the linker complains
that there already is a *.res file (LNK1241). I can link the one resource OR
the other. I also did not find a more detailed error description of
LNK1241.
The one resource script contains more or less static version info, the other
contains eventlog information as result of a compiled *.mc file, so I don’t
see a way to combine both resources into one file.
Suggestions where to look for information also are welcome.
Michael U. Müller
Abt. Biomedizinische Optik
Max-Planck-Institut für medizinische Forschung
Jahnstraße 29
D-69120 Heidelberg
Define and include only ONE “common.rc” in SOURCES. Then include
your different *.rc files into “common.rc” using
#include “your_rc_file_no1.rc”
#include “your_rc_file_no2.rc”
…
C.
----- Original Message -----
From: “Michael U. M?ller”
Newsgroups: ntdev
To: “Windows System Software Devs Interest List”
Sent: Tuesday, August 17, 2004 2:53 PM
Subject: [ntdev] How to link multiple compiled resource scripts
> How can I convince build / link to link more than one compiled resource
> script into one driver image? Is there a linker switch I did not find?
>
> Everytime when I include 2 *.rc files into “sources” the linker complains
> that there already is a *.res file (LNK1241). I can link the one resource OR
> the other. I also did not find a more detailed error description of
> LNK1241.
>
> The one resource script contains more or less static version info, the other
> contains eventlog information as result of a compiled *.mc file, so I don’t
> see a way to combine both resources into one file.
>
> Suggestions where to look for information also are welcome.
>
> Michael U. M?ller
>
> Abt. Biomedizinische Optik
>
> Max-Planck-Institut f?r medizinische Forschung
>
> Jahnstra?e 29
>
> D-69120 Heidelberg
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@compaqnet.be
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
Somebody nice already helped me.
You can only have one single *.res file, the linker does not accept a 2nd
one.
I just had to #include my second *.rc file into the first one generated
manually.
No further answers necessary.
Thank you
“Michael U. Müller” wrote in message
news:xxxxx@ntdev…
> How can I convince build / link to link more than one compiled resource
> script into one driver image? Is there a linker switch I did not find?
>
> Everytime when I include 2 *.rc files into “sources” the linker complains
> that there already is a *.res file (LNK1241). I can link the one resource
OR
> the other. I also did not find a more detailed error description of
> LNK1241.
>
> The one resource script contains more or less static version info, the
other
> contains eventlog information as result of a compiled *.mc file, so I
don’t
> see a way to combine both resources into one file.
#include one RC file to another.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
----- Original Message -----
From: “Michael U. Müller”
Newsgroups: ntdev
To: “Windows System Software Devs Interest List”
Sent: Tuesday, August 17, 2004 4:53 PM
Subject: [ntdev] How to link multiple compiled resource scripts
> How can I convince build / link to link more than one compiled resource
> script into one driver image? Is there a linker switch I did not find?
>
> Everytime when I include 2 *.rc files into “sources” the linker complains
> that there already is a *.res file (LNK1241). I can link the one resource OR
> the other. I also did not find a more detailed error description of
> LNK1241.
>
> The one resource script contains more or less static version info, the other
> contains eventlog information as result of a compiled *.mc file, so I don’t
> see a way to combine both resources into one file.
>
> Suggestions where to look for information also are welcome.
>
> Michael U. Müller
>
> Abt. Biomedizinische Optik
>
> Max-Planck-Institut für medizinische Forschung
>
> Jahnstraße 29
>
> D-69120 Heidelberg
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com