On Wed, 5 Oct 2016 15:40:46 -0400 Steven Gawroriski <[email protected]> wrote:
> Hello, > > On Wed, 5 Oct 2016 20:13:36 +0200 (CEST) > arnoldemu <[email protected]> wrote: > > > I want to make a solution for fossil so I can build fossil under > > visual studio itself from the IDE itself. I can then use the IDE's > > debugger. I tried to add all the source files from inside the src > > directory but that didn't work. So I then ran the batch file, waited > > for it to build and then used the source files from the msvcbld and > > that didn't seem to work either. > > > > So I have failed so far and wondered if anyone has made a solution > > and if they did, how did they do it? > > On Wed, 5 Oct 2016 14:30:34 -0400 > Richard Hipp <[email protected]> wrote: > > > Fossil uses a great deal of generated code. IDEs such as Visual > > Studio, on the other hand, are usually built around the assumption > > that all code is hand-written. Generated code is a more powerful > > concept, and ultimately makes development easier and less error > > prone. But since IDEs do not support it well, I think you will have > > difficulty putting together a "solution" for Fossil. > > Although it has been awhile since I last touched MSVC (I use Linux > now), what you would want is to setup a custom build rule in the MSVC > solution. Basically you can add an input source file which when ran > through the rule produces the resulting source code or alternatively > translates the source and then compiles it. The only issue would be > that you may have to have a set of virtual files and dependencies for > these autogenerated files if you do not want to do complete rebuilds > each time you want to compile. > > Depending on the maintainability requirements of the MSVC solution, > one that would require minimal maintaining is to just have a complete > build every time (always out of date), source code files that all use > a build rule that effectively does nothing, and a custom build step > which basically calls the batch file that exists at the root of the > Fossil repository. With a base template and a script (such as a POSIX > shell script), if a new source code file is added the script could be > ran which generates a new MSVC solution as required (and commit that > to the repository). Or instead of doing all of that, you could just have the project use the makefile that exists in `win/` and basically not worry about everything else. You would still need to specify the output executable name I believe (needed for debugging) along with arguments for execution and the working directory. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
