On Sun, Jun 26, 2011 at 2:13 AM, Orhun Birsoy <orhunbir...@gmail.com> wrote: > Hi, > I using 15+ open source projects for an application I am working on. I > maintain home grown python scripts to build most of the projects but others > are still manual process. In the pursuit of fully automating the process I > decided to try coapp and hopefully contribute the results back to coapp.
> I have some questions though: > 1. Since I will be using the development files : > > a. Is there a common place to 'install' the artifacts? (i.e. include/lib/bin > folders?) Is there an established directory structure? https://lists.launchpad.net/coapp-developers/msg00655.html > b. Is there an install-command (currently I am using building and installing > in build-command)? I'm not sure I understand what you're looking for here. > c. Is there an established naming for the configurations? I only see "x86" > and 'x64". I need to build both debug and release so I am currently building > both under x86 configuration for example. > This should still be ok, each build becomes its own package. Not sure if we've discussed -dbg yet > 2. Some projects need external tools to build, like cmake. Should there be a > coapp package to compile it as well? In my case it is already in my path so > I'll just use it in .buildinfo. CoApp hopes to have everything built by MSVC++ or similar (and maybe mingw in the distant future). There are some tools coming soon to help you convert a cmake project into a Visual Studio --Adam _______________________________________________ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp
