Regarding libphysfs in devpkg-mingw
Regarding libphysfs in devpkg-mingw
Hi,
It seems that the source of zlib is included in libphysfs, instead of being linked to zl - could you please change this?
It creates a "multiple definition" error for me when compiling with MINGW...
Also, please put up the devpkgs in the SVN instead. Having a unified source of files is better.
It seems that the source of zlib is included in libphysfs, instead of being linked to zl - could you please change this?
It creates a "multiple definition" error for me when compiling with MINGW...
Also, please put up the devpkgs in the SVN instead. Having a unified source of files is better.
Re: Regarding libphysfs in devpkg-mingw
I don't think we have someone who's keeping an eye for mingw devpkg. It's a bit trial and error with mingw, but I'm still using previous devpkg without issue...
The devpkg existence is fueled by the very idea of NOT putting them into SVN. Do you want to download all the different packages for every platform every time they'll change? What's for?
The devpkg existence is fueled by the very idea of NOT putting them into SVN. Do you want to download all the different packages for every platform every time they'll change? What's for?
Re: Regarding libphysfs in devpkg-mingw
Hi iNod, thanks for your reply.... I'll try to fix it myself, no problem...
Re: Regarding libphysfs in devpkg-mingw
That one is fixed.
If anyone wants libphysfs.lib without zlib, here it is..
If anyone wants libphysfs.lib without zlib, here it is..
- Attachments
-
- libphysfs.zip
- (229.67 KiB) Downloaded 294 times
Re: Regarding libphysfs in devpkg-mingw
Hmm.bornemix wrote:That one is fixed.
If anyone wants libphysfs.lib without zlib, here it is..
While I don't use mingw either, I am curious to know what compile options you used with physfs?
Which version of physfs is this anyway?
Can your version read in .wz files OK?
As for sticking everything in svn, that isn't going to happen. It is a huge PITA when bisecting code with svn.
All external libs are either on SF or GNA for mingw + macs + MSVC.
and it ends here.
Re: Regarding libphysfs in devpkg-mingw
I just added "HAS_ZLIB" with CMake/mingw-make static lib generation, so that it doesn't include the source of it, rather it needs to be linked when build wz, which is already done.
Its difference in size is about 20-30kb.
Its difference in size is about 20-30kb.
Re: Regarding libphysfs in devpkg-mingw
Well, the Mac project file automatically downloads the packages it needs. I wonder if we could make the Windows build scripts do the same thing...
Re: Regarding libphysfs in devpkg-mingw
That's what I'm doing now...
-
- Inactive
- Posts: 1695
- Joined: 01 Sep 2006, 19:17
Re: Regarding libphysfs in devpkg-mingw
win32/__BUILD_SCRIPT already does that for cross-compilation. Maybe you can adapt it to do native compiles as well?bornemix wrote:That's what I'm doing now...
Re: Regarding libphysfs in devpkg-mingw
I'm making a windows BAT that includes svn and 7zip, downloads mingw, bison, all dependencies, downloads svn/trunk, compiles it...
Is that already done?
Is that already done?
-
- Inactive
- Posts: 1695
- Joined: 01 Sep 2006, 19:17
Re: Regarding libphysfs in devpkg-mingw
The Linux script downloads and builds all dependencies, but uses the system tools and an already downloaded source. If you can adapt it, you just need a wrapper that downloads source etc, but not the building itself. I think it depends on bash and Gnu make, though.