search for: dll_export_view

On 11/14/11, Alan Garny wrote: > For what is worth, I have been able to trace my problem (thanks Kevin Kelley > for the indirect help!). The 'culprit' was DLL Expert Viewer > (http://www.nirsoft.net/utils/dll_export_viewer.html). It kept reporting > that there were no exported functions, so I (wrongly) assumed that something > had gone wrong while, using PEInfo > (http://www.pazera-software.com/products/peinfo/) I could see that > everything was, in fact, correct. There's also http://www.dependenc...

2011/11/15 Csaba Raduly <rcsaba at gmail.com>: > On 11/14/11, Alan Garny  wrote: >> For what is worth, I have been able to trace my problem (thanks Kevin Kelley >> for the indirect help!). The 'culprit' was DLL Expert Viewer >> (http://www.nirsoft.net/utils/dll_export_viewer.html). It kept reporting >> that there were no exported functions, so I (wrongly) assumed that something >> had gone wrong while, using PEInfo >> (http://www.pazera-software.com/products/peinfo/) I could see that >> everything was, in fact, correct. > > There's a...

For what is worth, I have been able to trace my problem (thanks Kevin Kelley for the indirect help!). The 'culprit' was DLL Expert Viewer (http://www.nirsoft.net/utils/dll_export_viewer.html). It kept reporting that there were no exported functions, so I (wrongly) assumed that something had gone wrong while, using PEInfo (http://www.pazera-software.com/products/peinfo/) I could see that everything was, in fact, correct. I have just tested things in my application and now everyth...

> >> GNU make is essential to msys build. I guess msysdtk would have it. > > > > I could find a copy of msysDTK at > > > http://sourceforge.net/projects/mingw/files/Other/Unsupported/MSYS/msy > > sDTK/, but not only is the 'latest' version a very old version > > (2003!), but once installed I couldn't find a copy of gmake in it. > >

...been able to build LLVM on Linux and Mac OS X, and it's all working fine as confirmed by a small LLVM test code that I wrote. However, on Windows, even though I get a DLL, that DLL doesn't contain any (exported) functions (according to DLL Export Viewer; see http://www.nirsoft.net/utils/dll_export_viewer.html). Now, I know that shared libraries are not supported on Windows using CMake (according to http://www.llvm.org/docs/CMake.html) which would have been my preferred building choice, but I didn't see anything against them not being supported using Autotools, so I thought I would try it...

2011/11/13 Alan Garny <agarny at hellix.com>: > Now, I know that shared libraries are not supported on Windows using CMake > (according to http://www.llvm.org/docs/CMake.html) which would have been my > preferred building choice, but I didn’t see anything against them not being > supported using Autotools, so I thought I would try it that way (as I > successively did on Linux

...optimization is enabled by default. The same for embedding libstdc++. Still, I thought I would give it a try and see how it goes. Anyway, the bottom line is that I got the usually 'big' DLL file, but... still no exported symbols (according to DLL Export Viewer; http://www.nirsoft.net/utils/dll_export_viewer.html). objdump reported more information though (including, possibly, some exported functions). Anyway, I tried to use the resulting DLL in my (Qt-MinGW based) application, but to no avail... So, kind of back to square one, sorry... :( I wish the documentation on how to build a shared version o...