Rastar Posted August 16, 2013 Share Posted August 16, 2013 Hi, how do your structure your source folders when developing for several platforms? By default, under Visual Studio and XCode, when you create new C++ classes they are created in the Project/Windows and Projects/MacOS folders. But many of them are (and should be) platform-independent, so I guess they should go under Source. However, I couldn't find a nice way to integrate that folder into a VS solution (it's possible under XCode, though). So: What's your preferred way of doing this? Quote Link to comment Share on other sites More sharing options...
AggrorJorn Posted August 16, 2013 Share Posted August 16, 2013 Do we have to take those folder layouts in account? If so, my projects are build completely wrong. I thought you would just make your project on one platform and then when you are ready for other platforms, you export it to those platforms. 1 Quote Link to comment Share on other sites More sharing options...
Rastar Posted August 18, 2013 Author Share Posted August 18, 2013 Probably the only time you have to take the folder layout into account is when your developing both for Windows and OSX. You can't publish from Windows to OSX (only to Android), and on OSX you can only publish to iOS. But developing for Windows and OSX doesn't work out of the box, or I haven't found out. When I create a new class in VisualStudio, it is created in Projects/WIndows. I then remove it again from the project, move it in the file system to "Source" and "Add existing item.." But this is cumbersome, of course - I hope there is an easier way for this. Quote Link to comment Share on other sites More sharing options...
Josh Posted August 18, 2013 Share Posted August 18, 2013 I never create files from Visual Studio itself. I just create a new text file in the Source folder and drag it into the VS project tree. Quote My job is to make tools you love, with the features you want, and performance you can't live without. Link to comment Share on other sites More sharing options...
Rick Posted August 18, 2013 Share Posted August 18, 2013 @josh why would you do that? That's for sure not the norm. Quote Link to comment Share on other sites More sharing options...
Josh Posted August 19, 2013 Share Posted August 19, 2013 Because I don't need VS auto-creating files for me who knows where. Quote My job is to make tools you love, with the features you want, and performance you can't live without. Link to comment Share on other sites More sharing options...
AggrorJorn Posted April 10, 2014 Share Posted April 10, 2014 Sorry to revive this topic again but I would like to know how this done with Linux in the picture. Should we use the Source folder for all de code or can we use the Project/Windows folder? Quote Link to comment Share on other sites More sharing options...
Admin Posted April 10, 2014 Share Posted April 10, 2014 I recommend keeping your source code in the "Source" folder and allowing all projects to access it. Quote Link to comment Share on other sites More sharing options...
Joshua Posted April 10, 2014 Share Posted April 10, 2014 I use the same method that Josh describes above. Right Click in the VS Solution Explorer->Select the 'Add Existing File'->Navigate to the Source directory->right click-> Create new Text Document.. I even put a shortcut to the Source folder in the Projects directory to make navigation a little easier. Quote Link to comment Share on other sites More sharing options...
AggrorJorn Posted April 13, 2014 Share Posted April 13, 2014 Maybe I am overlooking things here but how do you structure your files then? You can't add the folders structure you have in the source directory. Please don't suggest using filters. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.