UFO: Alien Invasion Issue Tracker
UFO: Alien Invasion
Go to the previous open issue
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
icon_project.png UFO: Alien Invasion / Closed Submit Patch #5113 Fix FreeBSD build. Better error for unsupported build target platforms.
Go to the next issue (open or closed)
Go to the next open issue
This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue basics
  • Type of issue
    Submit Patch
  • Category
    Not determined
  • Targetted for
    Not determined
  • Status
    Closed
  • Progress
  • Priority
    Not determined
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
  • Time spent
    100 hours
    Click here to see time logged against this issue
Issue details
  • Resolution
    RESOLVED
Attachments (2)
Duplicate issues (0)
This issue does not have any duplicates
Description
Today, I helped gehmehgeh get UFO:AI building on FreeBSD. The original build error had very little to do with the true cause.


It started off as a compile error about Com_DPrintf() being declared twice. We traced this down to HARD_LINKED_CGAME not being seen by the preprocessor. We finally traced this down to ${TARGET_OS}-config.h (i.e. freebsd-config.h) not being hard-coded into config.h. (The file "freebsd-config.h" was generated by ./configure.)


# I'm attaching a patch to config.h to add freebsd as a build target platform.
# I'm attaching a second patch to config.h to #error out if compiling on an unsupported build target platform. Debugging the issue was interesting, but it's something that can be largely avoided. With this #error, the problem will be obvious.


I also have a suggestion. Couldn't ./configure just write directly to config.h, or to a hard-coded target-platform-config.h, or perhaps the preprocessor could auto-generate the correct *-config.h filename? If we could do that, this issue will just go away for future unexpected build target platforms.
Todos (0 / 0)
Issue created
footer_logo.png The Bug Genie 4.3.1 | Support | Feedback spinning_16.gif