Show Posts
1
General / Manage a medium project, export and build on multiple platforms.
« on: February 08, 2023, 12:34:01 am »
Hi everybody
I've been developing SFML projects for a few months, alone and in collaboration, but I always have problems when expanding the scope: adding libraries, managing the code to be compile on linux and windows (this is by the many people working on a project), and exporting the final program.
My current approach is to use a makefile and the pre-compiled SFML libraries (GCC 7.3.0 MinGW (SEH) - 64-bit for windows and GCC - 64-bit for linux). Depending on the host, the makefile uses the version of the library that it needs and works, mostly.
In my last project, I tried to export my compiled program and tried to run on multiple platforms. And with that I think my approach demonstrates not to be the best. The big problem was that by default I was using the shared libraries, and I needed to put every .dll and .so inside the export folder. I tried to compile/use static SFML libraries but for some reason I can't do this. (as I'm not using any kind of IDE, I just got lost using makefiles....).
My big question after that is, how can I create a workflow that works for these needs? By workflow I mean a "simple" way to develop on linux, windows, and a way to export the project (win, linux, maybe mac?). Have any of you had to do something similar with this? Thanks!
I've been developing SFML projects for a few months, alone and in collaboration, but I always have problems when expanding the scope: adding libraries, managing the code to be compile on linux and windows (this is by the many people working on a project), and exporting the final program.
My current approach is to use a makefile and the pre-compiled SFML libraries (GCC 7.3.0 MinGW (SEH) - 64-bit for windows and GCC - 64-bit for linux). Depending on the host, the makefile uses the version of the library that it needs and works, mostly.
In my last project, I tried to export my compiled program and tried to run on multiple platforms. And with that I think my approach demonstrates not to be the best. The big problem was that by default I was using the shared libraries, and I needed to put every .dll and .so inside the export folder. I tried to compile/use static SFML libraries but for some reason I can't do this. (as I'm not using any kind of IDE, I just got lost using makefiles....).
My big question after that is, how can I create a workflow that works for these needs? By workflow I mean a "simple" way to develop on linux, windows, and a way to export the project (win, linux, maybe mac?). Have any of you had to do something similar with this? Thanks!