Menu
▾
▴
|
From: Dennis S. <sy...@yo...> - 2005-02-11 17:10:23
|
Heya fellahs, I'd like to try and get a libvisual.dll working under windows 32. Tho I've got >zero< experience with this. So what is needed to run the autotools, and gcc under windows ?, and how can we make sure that things like 'dlopen' are staticly linked ? Someone with clue on this subject, please step forward ;) It would be great if we could get a .dll working, which also might be a nice time to start working on C++ library bindings. Also, I'd like to start supporting the muine music player sometime near by creating C# bindings. Please I'd like to start a discussing about other platforms, and creating language bindings, participate in the discussion! :) Cheers, Dennis |
|
From: Vitaly V. B. <vit...@uk...> - 2005-02-11 19:05:56
Attachments:
A.diff
|
On Fri, 11 Feb 2005 18:10:14 +0100 Dennis Smit <sy...@yo...> wrote: $ unset CC CXX CFLAGS CXXFLAGS (I have a cross-compiler and stuff :) $ ./configure --host=i386-pc-mingw32 $ make fixes/hacks $ make fixes/hacks .... ... and here's successfully built non-working libvisual library :) patch to highlight problebatic places is attached. It's dlopen() related mostly.... -- Vitaly GPG Key ID: F95A23B9 |
|
From: Duilio J. P. <dp...@fc...> - 2005-02-11 19:29:36
|
> I'd like to try and get a libvisual.dll working under windows 32. > > Tho I've got >zero< experience with this. So what is needed to run > the autotools, and gcc under windows ?, I heavily suggest to use Cygwin+Mingw. Cygwin is a Posix emulation layer for Windows systems. Mingw stands for "Minimal GNU on Windows". You can build all the thing using Cygwin alone, but in that case the libraries are linked against libcygwin.dll.a, and you need to distribute it along with libvisual in your releases. But if you use Mingw, you link against Window's dlls, so the only thing needed is Windows itself. > and how can we make sure that > things like 'dlopen' are staticly linked ? dlopen on Windows requires special care, I will post more on this issue soon. You must also choose which installer to use, to start adjusting things for them. Bye, Duilio. |
|
From: Duilio J. P. <dp...@fc...> - 2005-02-11 19:32:58
|
Oh, and I forget to mention that some special care must be taken with the structure's packaging, and keep in mind, when you use asm, that the function's call convention on Windows is different from that of standard C, and the inline assembly usage will be different while compiling with Visual Studio. Bye, Duilio. |
|
From: Dennis S. <sy...@yo...> - 2005-02-14 18:16:13
|
On Fri, 2005-02-11 at 16:25 -0500, Duilio J. Protti wrote: > Oh, and I forget to mention that some special care must be taken with > the structure's packaging, and keep in mind, when you use asm, that the > function's call convention on Windows is different from that of standard > C, and the inline assembly usage will be different while compiling with > Visual Studio. Yep, we'll have to use gcc :) |
|
From: Duilio J. P. <dp...@fc...> - 2005-02-11 19:35:16
|
Oh, and I forget to mention that some special care must be taken with the structure's packaging, and keep in mind, when you use asm, that the function's call convention on Windows is different from that of standard C, and the inline assembly usage will be different when compiling with Visual Studio. Bye, Duilio. |
|
From: Dennis S. <sy...@yo...> - 2005-02-14 18:15:29
|
On Fri, 2005-02-11 at 16:21 -0500, Duilio J. Protti wrote: > You can build all the thing using Cygwin alone, but in that case the > libraries are linked against libcygwin.dll.a, and you need to distribute > it along with libvisual in your releases. But if you use Mingw, you link > against Window's dlls, so the only thing needed is Windows itself. I think we should go for mingw, I've been playing with it for a bit, not extremely succesful, but capable of running configure, and build a very small part of libvisual. As Vitaly already pointed out, it's borking a lot :) > > and how can we make sure that > > things like 'dlopen' are staticly linked ? > > dlopen on Windows requires special care, I will post more on this issue > soon. Yes please give me some more information regarding this. I think, for the windows platform we should really focus for a, works out of the box installer, probably including plugins for atleast winamp and windows mediaplayer. Is there a way of obtaining the standard header files for the windows platform, without the need to buy visual studio, or something ? > You must also choose which installer to use, to start adjusting things > for them. Any suggestions on this, I think we should go for an installer that is used a lot and is well known with the windows users. Cheers, Dennis |
|
From: Vitaly V. B. <vit...@uk...> - 2005-02-14 18:28:01
|
On Mon, 14 Feb 2005 19:15:26 +0100 Dennis Smit <sy...@yo...> wrote: > On Fri, 2005-02-11 at 16:21 -0500, Duilio J. Protti wrote: > > You must also choose which installer to use, to start adjusting things > > for them. > > Any suggestions on this, I think we should go for an installer that is > used a lot and is well known with the windows users. Inno Setup http://www.jrsoftware.org/isinfo.php should be a good choice. -- Vitaly GPG Key ID: F95A23B9 |
|
From: Dennis S. <sy...@yo...> - 2005-02-14 18:52:20
|
On Mon, 2005-02-14 at 20:27 +0200, Vitaly V. Bursov wrote: > On Mon, 14 Feb 2005 19:15:26 +0100 > Dennis Smit <sy...@yo...> wrote: > > > On Fri, 2005-02-11 at 16:21 -0500, Duilio J. Protti wrote: > > > You must also choose which installer to use, to start adjusting things > > > for them. > > > > Any suggestions on this, I think we should go for an installer that is > > used a lot and is well known with the windows users. > > Inno Setup http://www.jrsoftware.org/isinfo.php should be a good choice. Looks like neat software, I've written it down for when it's time :) Thanks for pointing out! Cheers, Dennis |
