Skip to main content
6 events
when toggle format what by license comment
Aug 14, 2015 at 19:10 comment added simbo1905 the conventions in my ecosystem are to prove config for only one command line build tool (there are three popular choices) which can generate the files of the popular IDEs. anyone can then build it with the command line tool which is the authoritive build which unit tests the code. since the popular tools maintain the capability to generate the IDE files no-one runs into such problems. only if somebody needed to add a very exotic feature which requires new build acrobatics would the question of changing the command line build to come up.
Aug 13, 2015 at 9:58 comment added JamesRyan Why not use a branch for the optional IDE? Theres no good excuse to enforce your preferred IDE on people, just make it clear that you are not committing to maintaining a 2nd one and the files are for use at your own risk. The first thing someone is going to do is get your project working in their preferred IDE, if you make that difficult you are just putting up a barrier to potential new contributors.
Aug 12, 2015 at 10:59 comment added Martijn "IDE specific" is tricky though. Project files and such may be good to include in the project, especially when it's non-trivial to constuct them from your build files. See also: stackoverflow.com/questions/347142/project-files-in-repository
Aug 12, 2015 at 10:43 comment added ArtOfCode @O.R.Mapper In general, I exclude any IDE specific files and just keep them on my hard disk - but personal preferences differ
Aug 12, 2015 at 10:34 comment added O. R. Mapper "good idea to exclude IDE config files from your repository" - I was a bit imprecise on this; it's the kind of IDE config files that you would want to keep in the repository. Not the kind that stores your local settings only valid for your machine, but the kind that tells the IDE where to find the files that belong to the project, how to build everything, etc.
Aug 12, 2015 at 10:10 history answered ArtOfCode CC BY-SA 3.0