- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
trying to compile some open source project with Qipo option in effect and notice that some public symbols defined in one of sources in following form
const void *const foo[]={
&bar1,
&bar2,
&bar3,
};
are not accesible in final objfile, making link error LNK2001 (unresolved external symbol). All other symbols exported are accessible. I use .def file to declare exports. This error doesnot happen if compiling respective sourcefile with /Qipo only so I suppose it might be a compiler eror.
Please for advice, if that's not a regular compiler error, what switches, pragmas or declaration generally should I use to be able make this code available for linker, keeping Qipo.
This is the IntelC++ version this error encountered on:
Intel 64, Version 12.0.0.104 Build 20101006
trying to compile some open source project with Qipo option in effect and notice that some public symbols defined in one of sources in following form
const void *const foo[]={
&bar1,
&bar2,
&bar3,
};
are not accesible in final objfile, making link error LNK2001 (unresolved external symbol). All other symbols exported are accessible. I use .def file to declare exports. This error doesnot happen if compiling respective sourcefile with /Qipo only so I suppose it might be a compiler eror.
Please for advice, if that's not a regular compiler error, what switches, pragmas or declaration generally should I use to be able make this code available for linker, keeping Qipo.
This is the IntelC++ version this error encountered on:
Intel 64, Version 12.0.0.104 Build 20101006
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is possible that these are inlined when you use /Qipo across files.
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page