| | [ Return to Bugs & Features | Roadmap 1.3 | Post Text | Post File | SVN ⇄ GIT | Prev | Next ]
STR #3112
| Application: | FLTK Library |
|---|
| Status: | 5 - New |
|---|
| Priority: | 1 - Request for Enhancement, e.g. asking for a feature |
|---|
| Scope: | 2 - Specific to an operating system |
|---|
| Subsystem: | Multiple |
|---|
| Summary: | whether we should define these macros in FLTK sourse files?(strdup stricmp...) |
|---|
| Version: | 1.3-feature |
|---|
| Created By: | zhuimengwuming |
|---|
| Assigned To: | Unassigned |
|---|
| Fix Version: | Unassigned |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
[ Post File ]
Trouble Report Comments:
[ Post Text ]
| |
| #1 | zhuimengwuming
18:17 Jul 18, 2014 |
| When I build FLTK fltk-1.3.x-r10221 with borland c++ 5.6(c++ builder 6),it has some errors,so I chaned like this paper,it works fine.and so I build it user Visual C++ 9.0 Express Edition ,it still work fine.so I am considering whether we should define these macros in FLTK sourse files? | |
| |
| #2 | greg.ercolano
19:12 Jul 19, 2014 |
| To fix this properly, we probably need to add Borland specific
exceptions to the macro checks. So lines like this:
# if defined(WIN32) && !defined(__CYGWIN__) && !defined(__MINGW32__)
..probably need to include something like: "&& !defined(__BORLANDC__)"
I'm just guessing. I don't have access to a Borland compiler. | |
[ Return to Bugs & Features | Post Text | Post File ]
|
| |
