Timeline for Can source code, automake and configure files for multiple OS co-exist in one Git branch
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 18, 2018 at 19:58 | answer | added | Lewis Pringle | timeline score: 1 | |
| Jul 9, 2018 at 5:18 | comment | added | txtechhelp |
industry practice for C++ projects that are OS agnostic ... #ifdef? ;)
|
|
| Jul 8, 2018 at 19:22 | comment | added | Bart van Ingen Schenau | Yes, you should have the configuration files for all platforms in the same branch. Keep in mind that the output from autogen, configure, make, etc. should not be stored in git at all. It contains information that applies only to your machine and will be different for other users. | |
| Jul 8, 2018 at 13:38 | comment | added | Nicol Bolas | The closest to "industry practice" you'll find for this is "Use CMake". | |
| Jul 7, 2018 at 21:08 | comment | added | Doc Brown | This is essentially the same questions for browser plugins and different target browsers, and the answer is pretty much the same as it should be here: have a single branch with two distinct build steps for each target platform. | |
| Jul 7, 2018 at 20:47 | review | First posts | |||
| Jul 8, 2018 at 7:38 | |||||
| Jul 7, 2018 at 20:44 | history | asked | picolo | CC BY-SA 4.0 |