[nanomsg] Re: Release packaging and build systems

  • From: Martin Sustrik <sustrik@xxxxxxxxxx>
  • To: nanomsg@xxxxxxxxxxxxx
  • Date: Thu, 25 Jul 2013 10:31:19 +0200

On 25/07/13 10:13, mike wrote:
I just modified a solution file for a simple project last night
(CppIEEmbed), and changed the version identifier in the solution to the
version I had. .. or rather I added the version 7.0 to something
supporting 8.0, 9.0, and 10.0. It worked.

This might work with NanoMSG depending on other complexities, such as
requiring Platform SDK updated include files or libraries. I think it
might be a very viable option to give a solution that can support the
max amount of versions, and then give a VC++ 6 project file for the
oldest (most used for static compiling) version.....

That's what cmake should be used for. In theory (I never checked it with multiple versions of MSVC myself) it should be able to detect the version of MSVC on the local machine and generate the appropriate solution file.

We should also allow the ability to compile a static library, as well as
a DLL... If you like, I would not mind contributing to this of NanoMSG
as a start to getting involved.

Yes. That would be nice. I recall it was a problematic topic back with ZeroMQ, but maybe you would be able to make it work.

I have every single virtual machine of
Windows (being a MSDN developer network user) and have enough space to
have continuous VMs specifically for nanomsg alone...

Wow! It would be nice to have at least 2-3 different win version in the CI environment. AFAICS buildbot slave can be run on windows. Do you happen to have an static IP address so that we can allow you to connect via our firewall?

Martin

Other related posts: