You can easily add a layer of protection against users accidentally mis-compiling this thing by adding a BuildDepends entry "fink-package-precedence", adding "-DCMAKE_CXX_FLAGS:STRING=-MD" to your cmake call, and then as an additional command at the end of the CompileScript:
The -MD flag causes the compiler to save additional data about the headers it found, and then the f-p-p program scans those data files and also the compiled binaries to detect various problems. As a bonus for maintainers, it also emits a list of packages that you definitely need to have as BuildDepends (you seem to have them all already).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This suite appears to use C++ code, so the .info needs to have a line "GCC: 4.0"
You can omit the BuildDepends entry "fink (>= 0.24.12)", as no OS X that is currently supported has ever had a fink older than that.
Last edit: Daniel Macks 2016-12-19
You can easily add a layer of protection against users accidentally mis-compiling this thing by adding a BuildDepends entry "fink-package-precedence", adding "-DCMAKE_CXX_FLAGS:STRING=-MD" to your cmake call, and then as an additional command at the end of the CompileScript:
fink-package-precedence --prohibit-bdep=sfml24-dev --depfile-ext='.d' .
The -MD flag causes the compiler to save additional data about the headers it found, and then the f-p-p program scans those data files and also the compiled binaries to detect various problems. As a bonus for maintainers, it also emits a list of packages that you definitely need to have as BuildDepends (you seem to have them all already).
What section do you think is best for this package? graphics? sound? libs?
Updated package (attached .tar.gz) thanks for taking a look!
Section "libs" would probably be best, as it is primarily of interest to developers. But I don't know. It does both graphics and sound.
Looks fine. Thanks for your contribution!