| Summary: | Platform specific headers and library inclusion | ||
|---|---|---|---|
| Product: | BpmCount | Reporter: | Werner Van Belle <werner> |
| Component: | Packaging | Assignee: | greg elliott <gelliott.spam> |
| Status: | ASSIGNED --- | ||
| Severity: | normal | CC: | werner |
| Priority: | Future | ||
| Version: | 0.1 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
|
Comment 3
greg elliott
2008-08-31 20:40:34 CEST
That is how I would do it as well, so we could start with various defines files if interested. (In reply to comment #0) > Hello, > > Do you have any plans on how to structure platform specific includes and > headers. The source fole os-specific-headers.h is already a very good start, > but certain compile options are so platform dependend that they belong in the > makefile. BpmDj relied on the concept of defines files. A file which must be > available for the specific platform and wich would be included in the makefile. > I personally believe this is the easiest way of solving platform specific build > options, but feel free to suggest any other possible option. > my opinion is that the os-specific-headers.h file is fine. it's working, is a single file that works for all 3 major operating systems, and is clean. for me, the only things that should go in a separate defines files should be locations of libraries and headers and compilers. Hello, Do you have any plans on how to structure platform specific includes and headers. The source fole os-specific-headers.h is already a very good start, but certain compile options are so platform dependend that they belong in the makefile. BpmDj relied on the concept of defines files. A file which must be available for the specific platform and wich would be included in the makefile. I personally believe this is the easiest way of solving platform specific build options, but feel free to suggest any other possible option. |