Author | Topic: Re: Error - DLL couldn't be loaded | |
---|---|---|
James Loughner View the complete thread for this message in: | Re: Error - DLL couldn't be loaded on Mon, 05 Dec 2011 14:31:16 -0500 Looks like this DLL is dynamically linked but then again maybe it is a static link preformed in yet another XPJ. If it is a static link then you need to build the whole project to get it to work I think. You may want to try my IDE it may help sort this monster out. Note the bat file is redundant all can be done from a single xpj http://gogalthorp.com/splash Jim On 12/05/2011 02:18 PM, semmelbroesel wrote: > Hi, thanks for your fast reply! > > Basically, my predecessor was still mentally stuck in DOS mode, hence > the batch file I guess. > The batch file basically runs pbuild for every module of the project. > > I supposed I could run the files directly from the development > directory, but then I'd have to copy a bunch of database files over, > too, and I'm using one computer only to house the development stuff and > one that holds the complete product folder. > > I know I'm using the same version as the other person - their computer > is a mess, so we haven't found the licensing information for alaska yet, > so I installed a trial version and overwrote it with the alaska program > folders until we can figure this out. > So I know that I'm likely missing a few PATH definitions, so during my > compile attempts I noted all the missing libraries and includes, found > them in other folders and copied them into the main alaska include and > lib folders, and the compilation seemed to work fine after that. > That's another issue - I don't even know what other tools and libraries > they used - I know the XBTools are involved, and I found those. > We're using pbuild version 1.90.355 if that helps. > > Here's the content of the XPJ file in question: > > === > MYFILE.XPJ Project File > /n /w /m /b /ga > [PROJECT] > COMPILE = xpp > COMPILE_FLAGS = /q /dll:DYNAMIC > DEBUG = no > GUI = yes > LINKER = alink > LINK_FLAGS = > RC_COMPILE = arc > RC_FLAGS = -v > MYFILE.XPJ > > [MYFILE.XPJ] > MYFILE.DLL > > [MYFILE.DLL] > > $START-AUTODEPEND > wFamily.obj > wOpenFile.obj > wGroup.obj > MYLIB.LIB > MYLIB2.LIB > DCLIPX.LIB > DCLIP1.LIB > XPPUI2.LIB > XBTBASE1.LIB <-- import Tools libraries added > XBTBASE2.LIB > DCDESIGN.LIB > > $STOP-AUTODEPEND > wFamily.prg > wGroup.prg > wOpenFile.prg > wMealGrp.prg > === > > Thanks for your help! > > > > On 12/5/2011 1:01 PM, James Loughner wrote: >> Hi and welcome >> Hard to tell from the information you give. Not sure what the copying >> you mention is for. Normally you have a development directory where you >> compile all things and test before copying to the production directory. >> >> Not sure why you have a bat file normally it is not needed, but we have >> no idea how your predecessor set things up. Seems needlessly complicated >> to me. I doubt the problems comes from corruption in the source or xpj >> files since they would error out on compile. >> >> Are you sure that all the app has been compiled with the same version of >> Xbase++?? >> >> Maybe show us the XPJ file. >> >> Jim >> |