Re: [Mingw-w64-public] experimental 4.7 std::thread enabled build by rubenvb

[Ruben V. B. <van...@gm...>]

2012/10/10 Joshua Boyce <rap...@ra...>

> On Fri, Aug 17, 2012 at 4:34 AM, Ruben Van Boxem <van...@gm...
> > wrote:
>
>>
>> I never meant to say it was as solid and full-featured as GCC on Windows.
>> What I meant was that the program you call ("clang"/"clang++", i.e. the
>> "compiler driver") can be used as a drop-in replacement for "gcc"/"g++",
>> unlike for example Visual Studio's "cl".
>>
>> Now that I have fixed my 4.7.1-1-release debacle, and actually have
>> useful Linux64 builds, I can check out this problem.
>>
>>
> Hi Ruben,
>
> Sorry to necro-bump this thread, but I have just run into the same issue
> with exporting functions from a shared library on Windows when using Clang.
>
> Has any progress been made in finding a solution or workaround?
>

This hasn't been implemented in Clang yet (AFAIK). A workaround is of
course using a .def file, but that's quite tedious. I suppose a hacky
"-Wl,--export-all-symbols" could be considered a workaround, but not at all
a solution, nor recommended really.

Remember, there's like, half a person working actively on Windows
LLVM/Clang support, don't expect too much changes too soon. I find this
*very* unfortunate, but I am not capable of helping the project, nor do I
have the time anymore to try :-/

Cheers,

Ruben


>
> Thanks.
>
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> Mingw-w64-public mailing list
> Min...@li...
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
>