Hello list readers,

i'm a newcomer to this list. i'm Pierre, and i've been playing with mingw-w64 
for the past 3 days. i have been gathering help from the original mingw project 
list, the guys were very helpfull here. So now i'm facing more mingw-w64 
issues, i'm subscribing to this list upon advice from one of the mingw user.

So basically, i have set up a mingw-w64 installation from SeZero prebuilt 
packages and MSYS environement. This perfectly works for me for basic stuff 
like compiling and linking to libraries made with mingw-w64.

However, when it comes to delay-loaded linking (And that's the only reason i 
switched from mingw to mingw-w64 after dropping MSVC), i find myself stuck on 
two scenarios:
1) My project builds various libraries, and i wish to delay-load them.
2) My project has to link against proprietary libraries (Canon, Epson, Panini 
scanner APIs) for which i don't have source code.

i am really willing to continue using mingw-w64, so the only problems keeping 
me from successfully building my project are those two described here.

For now, i first would like to solve the first case scenario. My project's 
libraries export various methods, most of them being C++ (So the library 
actually exports full classes definitions).

To allow delay-loading (And since i'm using Qt as my IDE, my "makefiles" are 
actually Qt's .pro files), i do something like this:
#    QMAKE_POST_LINK +=  gendef "$${MAINBINDIR}/$${TARGET}.dll" && \
#                        dlltool \
#                            --input-def "$${TARGET}.def" \
#                            --output-delaylib 
"$${MAINBINDIR}/lib$${TARGET}.delayed.a" \
#                            "$${MAINBINDIR}/$${TARGET}.dll"
This extracts .def, and then creates libName.delayed.a, NAME being substitued 
with the target name. These commands are issued without any errors, and the 
output is good.

Here, no problem. The main binary then links against libName.delayed.a, and it 
gets compiled fine. However, when trying to start the binary, it just won't. 
Nothing happens at all, not even a "missing DLL" symptom break.

Is there anyone here with a clue of what i'm doing wrong? Once these problems 
will be solved, i will request your kind help and knowledge again about the 2nd 
case scenario, which is more of a problem but i may be able to solve it myself 
if i understand what i'm doing wrong on the libraries over which i have full 
control.

Thanks a lot,
Pierre.


------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to