RE: Memory leaks & memory access errors

This does sound like a good solution.

We are not currently dead in the water with Visual Studio 2003 since
it seems that Visual Studio 2003 is able to open Visual Studio .NET
solutions and properly build the software.  The same could not be said
for the previous release.

Bob

On Mon, 9 Feb 2004 [email protected] wrote:

> Here is an interesting reference to a potential solution the "configure"
> problem on Windows.
>
> http://software.ericsink.com/
>
> As many of you know, configure is the wizard like application that currently
> generates Visual Studio compatible projects and solutions. It has not yet
> been revised to handle VS 2003 format which has changed yet again. The
> thought of doing yet another rev to this app is more then I can take :-(
>
> It seems like the CMake might be one way to move to a better system, since
> configure has always been a big hack.
>
> Thoughts?
>
> -Bill
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> Graphicsmagick-core mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/graphicsmagick-core
>

======================================
Bob Friesenhahn
[email protected]
http://www.simplesystems.org/users/bfriesen



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn