32 / 64 bit development in linux mint 17.1 |
32 / 64 bit development in linux mint 17.1 |
Rainer Deyke
Guest
|
On 20.01.2015 07:13, arthurtonypark wrote:
I wouldn't rely on the development libraries provided by the package manager, as they tend to be out of date. Compile from source, using one --prefix for 32 bit and another for 64 bit. -- Rainer Deyke _______________________________________________ SDL mailing list http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org |
|||||||||||||
|
32 / 64 bit development in linux mint 17.1 |
Daniel Gibson
Guest
|
Hi,
yeah, this doesn't seem to work with the mint 17.1 packages - the actual conflict seems to be in libavahi-client-dev:i386 which seems to uninstall libavahi-client-dev:amd64 (and everything that depends on it). libsdl2-dev depends on libpulse-dev depends on libavahi-client-dev The "sane" thing to do, IMHO, is to either * unpack libSDL2.so from the i386 dev package - like you did, but you don't have to put it into /usr/libs/i386-linux-gnu, you can just put it anywhere and tell the compiler to use that path to find libs (-L/your/path) for i386 * compile libSDL2 for i386 yourself and tell the compiler to use that version to link against (again with -L/your/path) for i386 Cheers, Daniel On 01/20/2015 07:13 AM, arthurtonypark wrote:
_______________________________________________ SDL mailing list http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org |
|||||||||||||
|
arthurtonypark
|
Thanks for the replies. I'll look at building from source.
|
|||||||||||
|
Magnet
|
An old trick I used to use was when running a 64 bit OS, is to create a 32 bit chroot system inside your current system. You can then mount it anytime and run / compile 32 bit programs when needed using the default package manager/compiler. It takes up some space but is a lot better then dual booting or messing with libraries and and other stuff. Otherwise VMware is a good options as well to install 64 and 32 bit systems to compile and test stuff on. |
|||||||||||||
|