[cfe-dev] Linking Errors on Windows Part 2

[Ryan Gonzalez]

I AM exporting the functions I need. What I'm saying is that when use
__declspec(dllexport), ld tells me that every exported symbol is undefined.
THe dumpbins of the object file clearly show the symbols.


On Mon, Oct 14, 2013 at 11:08 AM, Reid Kleckner <rnk at google.com> wrote:

> You probably need to apply __declspec(dllexport) to the functions you wish
> to export.  Unlike on Linux, on Windows nothing is exported by default, and
> you have to list your exports manually.  There is no way to export
> everything.
>
>
> On Sun, Oct 13, 2013 at 1:50 PM, Ryan Gonzalez <rymg19 at gmail.com> wrote:
>
>> Ok, I've done some more research on the linking issue I mentioned in my
>> last thread/post/whatever. Summary: Object files build using Clang won't
>> link into a Python extension because ld says the init function is "not
>> defined".
>>
>> It seems, however, that this happens when linking any shared library! I
>> recently tried to build Shiboken and the same errors appeared. Every
>> exported function is listed as "not defined".
>>
>> I wanted to post this again because it isn't due to the MS ABI
>> underscores like I originally though.
>>
>> --
>> Ryan
>>
>> _______________________________________________
>> cfe-dev mailing list
>> cfe-dev at cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>>
>>
>


-- 
Ryan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20131014/d8c11cc6/attachment.html>