Comments on: Calc Solver release

By: Kohei Yoshida

Kohei Yoshida — Fri, 30 May 2008 14:54:15 +0000

I’ve received similar problem from a Spanish user. It’s supposed to fall back to English (not Russian) if the translation is not available for the current locale. I’ll look into it.

By: Clovis Tristao

Clovis Tristao — Fri, 30 May 2008 04:02:35 +0000

Hi,

I´m installed SCSolver in OO 2.4 (Portuguese Brazil), and the system language should not be automatically picked up and the appropriate translation texts. Appear Russian Language.

What´s happening?

Thanks a lot, sorry my English.

Clóvis Tristão

By: alex

alex — Tue, 18 Dec 2007 12:08:43 +0000

lpsolve is the best )

By: Kohei Yoshida

Kohei Yoshida — Tue, 27 Nov 2007 16:15:29 +0000

Great answer! Thanks a lot, Tor. :-)

Looks like MSYS will be a very attractive option. OTOH, I don’t mind so much on relying on Visual Studio’s build system, as long as I can invoke it from the command line & I can check in the build script. I just want to use whatever system is “native” to the target platform.

By: Tor Lillqvist

Tor Lillqvist — Tue, 27 Nov 2007 12:51:50 +0000

> what do Windows developers use these days to build C++ projects?

The great unwashed masses of course use Microsoft Visual Studio, full frontal GUI everything, have never used anything else. and are happy with that…

People from a more Unixish background, porting software originating from Unix that use some GNUish autoconfused buld system, often use the same also on Windows. I.e. autoconf, automake, libtool etc. If you want to go this way, stay away from Cygwin. It will only cause confusion, as you have noticed.

(OOo is built on Windows using Cygwin, sure, but they have to use lots of tricks to work around pitfalls.)

Cygwin is more or less a separate operating system just running on top of Windows.

Instead of Cygwin, use MSYS. It is technically a fork of Cygwin, but with some crucial changes, and a different raison d’être. MSYS (together with “mingw”, which is gcc and GNU binutils targeted for Win32) is intended just to be a development environment for native Win32 software, while Cygwin comes with a development environment for Cygwin software, so if you actually want to build non-Cygwin (”native Win32″) software on Cygwin, you have to be very careful, not to mix up things.

MSYS, when starting a non-MSYS programs, translates command-line arguments that look like file names in the Unix format into the corresponding native format with drive letters. It also translates PATH-style environment variables when starting non-MSYS programs. This means that you don’t have to worry about not passing “Cygwin” (Unixish) pathnames to native programs, like you have to when using Cygwin.

Hope this helps…