Spending a few minutes to ensure that all platforms are consistent will pay off later.Ĭlean up your template. VS2008 seems to be insane and drops output folders all over the place, with the default locations of Win32 and 圆4 output differing. That way you can jump into a single directory to test all your tools and/or wrap them up for a binary distribution. (optional) I set up my paths in the visual studio project files so that everything is built in the project directory, then I have a post-build step copy just the dll/exe/pdb files I need to $(SolutionDir)$(OutDir). This is going to be your "template" so you don't want to edit it after you've made 20 copies. Here's what I did in Visual Studio 2008:Ĭreate your first Win32 command line tool project, get all your settings down for all platforms and make sure it works under all circumstances. It turns out it can be less horrible than I had thought, though it still sucks. Personally, I have decided to go with the "many small projects" solution and just deal with it. NET projects! Well, you can make a wizard if you want to wade through the docs on doing that I suppose. You can't even make a project template like you can with. Use a build tool that does not integrate well with Visual Studio, like GNU make. Use MSBuild and deal with its steep learning curve. So I've been looking into this for a while now and the solutions all leave much to be desired.
GOODWAY TOOLS WINDOWS
I'd like to stick with the standard Windows toolchain as much as possible. I'm really not interested in using cygwin's gcc/mingw or NAnt. Is there a nice way of building all the tools from a single "thing" (project, msbuild file, etc.)? c file are excluded from the build but that would make building all the tools at once impossible. I've thought about using different configurations where all but one. On unixy systems you can use a makefile to do this easily but the most naive transformation to the windows / Visual Studio world involves making a separate project for each tool which, although it works, is a lot of work to set up and synchronize and more difficult to navigate at both the filesystem and project/solution level. c files (say 20 or so) that are compiled into command-line tools, each with their own main() function, that will use the library. This source consists of a few files which will create a library and a lot of small.
GOODWAY TOOLS CODE
Suppose you have some source code that comes from the unix world.
0 kommentar(er)
