[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [fluid-dev] FluidSynth 1.1.2 release planning

From: Sven Meier
Subject: Re: [fluid-dev] FluidSynth 1.1.2 release planning
Date: Thu, 15 Jul 2010 13:07:00 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20100527 Thunderbird/3.0.5

Hi Pedro,

yes, I'm building fluidsynth on Windows with CMake and mingw.

I don't really care about the library name, it should just stay consistent for the next releases.


On 07/15/2010 10:06 AM, Pedro Lopez-Cabanillas wrote:
On Wednesday, July 14, 2010, Sven Meier wrote:
building fluidsynth with MinGW results in "libfluidsynth.dll",
previously the library was named "libfluidsynth-1.dll". Is this change
I suppose that you are testing the CMake build system in windows with the
mingw compiler. I didn't realize about the name change, so I don't think that
it was intended. The new naming scheme comes from using the same
specification to generate all the project files and makefiles in all
platforms, so the library name would be "libfluidsynth" everywhere.

Consistent naming may be good, but at the same time there is the problem that
windows DLL's don't have a SONAME atribute like the Unix libraries, so it
would make sense to include the LT_VERSION_CURRENT number in the library
name, like the autotools does in windows resulting in "libfluidsynth-1.dll".
This may be done also in all platforms, including Linux, if we want. It would
be like, for instance, the "dbus-1" library.

By the way, CMake is currently generating a fake ".la" file for the library.
This is a deprecated libtool file, and I would like to comment out the
generation leaving it it place just in case somebody needs it.

There are also different library names for debug/release versions. The MSVS
project files in the SVN repository generate a "libfluidsynth.dll" for the
release configuration, and "libfluidsynth_debug.dll" for debug. The MSVS
projects generated by CMake create the same library name "fluidsynth.dll" for
all configurations. It may be possible to change this behavior if needed.

What do you think?


fluid-dev mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]