coapp-developers team mailing list archive

[Garrett Serack <garretts@xxxxxxxxxxxxx>]

Yeah, the libjpeg one had the .vcxproj files already.

With ones that don't have any vcxproj files, we just need to get it to compile.

Any. Way. We. Can.

After that, the mkSpec and mkProject tools will do all the heavy lifting to creating real, useful, consistent .vcxproj files that we can use after that.

If there are make/nmake files, for now, use that.
If there is a VC6,7,8 or 9  project file that can be converted, for now, use that.
If there is a batch file, for now, use that.
If all there is is source code alone, try making a command line like : cl *.c  .. if that works, use that (see the grep .buildinfo file at https://github.com/coapp-packages/grep/blob/master/COPKG/.buildinfo )


It just takes a reliable, consistently reproducible build, and we will be able to automate the creation of the rest.

G

________________________________________
From: Adam Baxter [voltagex@xxxxxxxxxxxx]
Sent: Thursday, May 12, 2011 6:58 PM
To: Garrett Serack; coapp-developers@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Coapp-developers] Blogged: "Shallow-forking a project" for #CoApp

So the libjpeg example in your post already had .vcxproj files for it?

What extra steps would be required for a project that's never had a
Windows/Visual C++ build? Let's assume for the moment that it'd be
simple enough not to require any Windows-specific code changes, and
that we're only talking about taking make/automake files and
converting the build process over for Visual Studio.

On Tue, May 10, 2011 at 7:27 AM, Garrett Serack <garretts@xxxxxxxxxxxxx> wrote:
> Rather than cross post that, you can see the post here:  http://j.mp/jCZT8w
> G
> _______________________________________________
> Mailing list: https://launchpad.net/~coapp-developers
> Post to     : coapp-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~coapp-developers
> More help   : https://help.launchpad.net/ListHelp
>
>