On Mon, 17 May 2010, Adam Tkac wrote:
As I wrote above I will test MS Visual Studio 2010 Express. If it will
work fine then I will update *dsp build scripts and I will start to
maintain them, it shouldn't be so hard. I agree with you that for
Windows only developers Visual Studio environment is
On Mon, May 17, 2010 at 04:52:09PM +0200, Peter Åstrand wrote:
On Mon, 17 May 2010, Adam Tkac wrote:
As I wrote above I will test MS Visual Studio 2010 Express. If it will
work fine then I will update *dsp build scripts and I will start to
maintain them, it shouldn't be so hard. I agree with
On 5/17/10 9:52 AM, Peter Åstrand wrote:
Wouldn't it make more sense to fix the problems with MinGW instead? If
the official downloads are bad, we can provide our own
MinGW-for-windows. Shouldn't be very difficult. Sounds more fruitful
than trying to maintain multiple build systems.
Windows
I personally find IDE's more of a struggle than command line tools.
Plus, switching to a new IDE would be a lot more trouble than simply
converting and fixing the existing DSP files. Additionally, we'd still
have to use Visual C as the underlying compiler. It's not that building
TigerVNC from
On 5/17/10 12:18 PM, Peter Åstrand wrote:
Per my previous message, there are a lot of additional components
required, not just MinGW. We'd have to distribute the necessary MSYS
components as well.
MSYS is a part of the MinGW project; not a big problem.
In total, this would amount to
