|
From: Glen <gle...@mo...> - 2005-03-11 18:45:47
|
Wicked!!! thanks Leif... For the time being I found the vc project file in the src/c directory and got the build working in VC .net. I will next try the build.bat and see how that goes... ***10 minutes later*** Okay that worked excellently and I can clearly see how the .in files work (smart). Sorry I didn't see that myself. I saw the make files and the .in files and immediately thought linux ./configure and didn't look any further (a good example of knowlege getting in the way)... I also see Rune's response as well outlining the changes for VC++ .net 2003 and will go through and see if those changes work... Leif Mortenson wrote: > Glen, > > Glen wrote: > >> There is no developper list so I figured I would try here. I am >> trying to build wrapper.exe using the makewin32.bat. That is using >> MS vc++ 98. I have vc++ 7.0 (the one that comes with .net pro >> 2003). Does anyone know how I could either >> >> * obtain a copy of ms vc++ 98 that is currently used for the win32 >> build (I am willing to $$$$ it but am not 100% sure what to buy) >> * make the necessary changes to get the vc++.net compilre working >> with it >> > Just answered you offline on this. But try running build.bat in the > src root directory. > There may be a few changes need for .net but they should be simple. I > never use > C for much other than the Wrapper so have never had the need to > upgrade my > copy of vc++. > > I would appreciate you posting any changes that are required to get > things working > with the vc++ .net. > >> One other aside question. I noticed a few files missing where the >> missing file was there just with a .in extension. Is there special >> processing that needs to be done on these or is just removing the .in >> extension fine? I vaguely remember something on linux with these >> files where you ./configure but not sure how to get that to work on >> win32. > > > The .in files are source files used by the ant build to generate the > actual source files > used by the Vc++ compiler. If you run build.bat then they will be > generated for > you. They include such things as the version number and build time > of the Wrapper. > for inclusion in the binaries and jar file. > >> Last question how is the win32 build currently done? > > > run build.bat. > > To create an actual release, run "build.bat release" on any platform. > > Cheers, > Leif > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |