Author Topic: MacOSX build process broken due to SVN 5694 commit  (Read 6144 times)

0 Members and 1 Guest are viewing this topic.


 
Re: MacOSX build process broken due to SVN 5694 commit
Fixed in 5698.

Next time, please include some more information than 'it's borked'!

Issue was that disableWindowsKey was moved from within WinMain (protected by _WIN32 ifdef) into game_main (not protected by _WIN32 ifdef)
STRONGTEA. Why can't the x86 be sane?

 

Offline Tinman

  • 27
  • Released: WCS mini campaign
Re: MacOSX build process broken due to SVN 5694 commit
Next time, please include some more information than 'it's borked'!
I'll do.
But as the 5694 commit was only the Windowskey-thing I thought that was clear  :)

Thanks for the fast response!

 

Offline chief1983

  • Still lacks a custom title
  • Moderator
  • 212
  • ⬇️⬆️⬅️⬅️🅰➡️⬇️
    • Minecraft
    • Skype
    • Steam
    • Twitter
    • Fate of the Galaxy
Re: MacOSX build process broken due to SVN 5694 commit
Yeah I'll admit, that was even my hunch just after looking at the diff :)
Fate of the Galaxy - Now Hiring!  Apply within | Diaspora | SCP Home | Collada Importer for PCS2
Karajorma's 'How to report bugs' | Mantis
#freespace | #scp-swc | #diaspora | #SCP | #hard-light on EsperNet

"You may not sell or otherwise commercially exploit the source or things you created based on the source." -- Excerpt from FSO license, for reference

Nuclear1:  Jesus Christ zack you're a little too hamyurger for HLP right now...
iamzack:  i dont have hamynerge i just want ptatoc hips D:
redsniper:  Platonic hips?!
iamzack:  lays

 

Offline Tinman

  • 27
  • Released: WCS mini campaign
Re: MacOSX build process broken due to SVN 5694 commit
Not the best thread to mention it: but the MacOS X building process is broken again.  :p
As far as I can see it is SVN5715 (with a lot of errors)
One of the MacOS X developers may have to look into this  :)

 

Offline Zacam

  • Magnificent Bastard
  • Administrator
  • 211
  • I go Sledge-O-Matic on Spammers
    • Minecraft
    • Steam
    • Twitter
    • ModDB Feature
Re: MacOSX build process broken due to SVN 5694 commit
Nope. Update to 5716. Portej forgot to sync the new gropenglpostprocessing.cpp anh .h files when he merged Antipodes into Trunk.
Report MediaVP issues, now on the MediaVP Mantis! Read all about it Here!
Talk with the community on Discord
"If you can keep a level head in all this confusion, you just don't understand the situation"

¤[D+¬>

[08/01 16:53:11] <sigtau> EveningTea: I have decided that I am a 32-bit registerkin.  Pronouns are eax, ebx, ecx, edx.
[08/01 16:53:31] <EveningTea> dhauidahh
[08/01 16:53:32] <EveningTea> sak
[08/01 16:53:40] * EveningTea froths at the mouth
[08/01 16:53:40] <sigtau> i broke him, boys

 

Offline Tinman

  • 27
  • Released: WCS mini campaign
Re: MacOSX build process broken due to SVN 5694 commit
Yes. I used SVN5716 to build fs2Open (and added the files of 5716 manually to the XCode project) but it throws 24+ errors
(I tested SVN5713: build process ok)

 

Offline Zacam

  • Magnificent Bastard
  • Administrator
  • 211
  • I go Sledge-O-Matic on Spammers
    • Minecraft
    • Steam
    • Twitter
    • ModDB Feature
Re: MacOSX build process broken due to SVN 5694 commit
Hmm. Hery's original commit of postprocessing to Antipodes included xcode updates, as did portej's port of it to Trunk. See the patch in my latest Test Build for confirmation.

What are the errors that it throws? And can you revert or checkout a 5713 and apply the postprocessing.patch from my Test Build post and see if it does the same behaviour?
Report MediaVP issues, now on the MediaVP Mantis! Read all about it Here!
Talk with the community on Discord
"If you can keep a level head in all this confusion, you just don't understand the situation"

¤[D+¬>

[08/01 16:53:11] <sigtau> EveningTea: I have decided that I am a 32-bit registerkin.  Pronouns are eax, ebx, ecx, edx.
[08/01 16:53:31] <EveningTea> dhauidahh
[08/01 16:53:32] <EveningTea> sak
[08/01 16:53:40] * EveningTea froths at the mouth
[08/01 16:53:40] <sigtau> i broke him, boys

 
Re: MacOSX build process broken due to SVN 5694 commit
Zacam: I probably screwed something up - I've got no way of testing Xcode files
(sorry about forgetting gropenglpostprocessing.cpp/h - fixed now though!)
STRONGTEA. Why can't the x86 be sane?

 

Offline Zacam

  • Magnificent Bastard
  • Administrator
  • 211
  • I go Sledge-O-Matic on Spammers
    • Minecraft
    • Steam
    • Twitter
    • ModDB Feature
Re: MacOSX build process broken due to SVN 5694 commit
****. It seems my .patch nor Hery's original .patch included xcode data. Frak.
Report MediaVP issues, now on the MediaVP Mantis! Read all about it Here!
Talk with the community on Discord
"If you can keep a level head in all this confusion, you just don't understand the situation"

¤[D+¬>

[08/01 16:53:11] <sigtau> EveningTea: I have decided that I am a 32-bit registerkin.  Pronouns are eax, ebx, ecx, edx.
[08/01 16:53:31] <EveningTea> dhauidahh
[08/01 16:53:32] <EveningTea> sak
[08/01 16:53:40] * EveningTea froths at the mouth
[08/01 16:53:40] <sigtau> i broke him, boys

 

Offline Echelon9

  • 210
Re: MacOSX build process broken due to SVN 5694 commit
I also noticed that commit 5715/5716 (Antipodes #4) didn't update the Xcode project file. I've updated my local Xcode project file and am running a test build now.

Results should be available soon - and I can commit my locally change Xcode project file if all is green.

Update: Xcode project file has been updated so that the gropenglpostprocessing.cpp/h files are included. I committed a small fix to address GCC's capitalisation requirements for MIN(). Compile issues still remain at present, further work needed.
« Last Edit: December 15, 2009, 01:01:26 am by Echelon9 »

 

Offline Zacam

  • Magnificent Bastard
  • Administrator
  • 211
  • I go Sledge-O-Matic on Spammers
    • Minecraft
    • Steam
    • Twitter
    • ModDB Feature
Re: MacOSX build process broken due to SVN 5694 commit
Sweet. Thank you, Echelon9. I'm pretty sure my notepad hack job in 5718 wasn't going to do it.

FYI, there was a line added to xcode in the merge (4949) that according to chief was removed for a reason. Keep that in mind if you need to and feel free to pluck it back out if you have to.
Report MediaVP issues, now on the MediaVP Mantis! Read all about it Here!
Talk with the community on Discord
"If you can keep a level head in all this confusion, you just don't understand the situation"

¤[D+¬>

[08/01 16:53:11] <sigtau> EveningTea: I have decided that I am a 32-bit registerkin.  Pronouns are eax, ebx, ecx, edx.
[08/01 16:53:31] <EveningTea> dhauidahh
[08/01 16:53:32] <EveningTea> sak
[08/01 16:53:40] * EveningTea froths at the mouth
[08/01 16:53:40] <sigtau> i broke him, boys

 

Offline Tinman

  • 27
  • Released: WCS mini campaign
Re: MacOSX build process broken due to SVN 5694 commit
I don't know if it is of any help, but this are some error-messages (after SVN5719)

[attachment deleted by admin]

 

Offline Hery

  • 26
Re: MacOSX build process broken due to SVN 5694 commit
That was obviously my fault. Looks like I confused object types while merging old shaders management code with the shaders manager.
I'm already solving that problem.

 

Offline Echelon9

  • 210
Re: MacOSX build process broken due to SVN 5694 commit
Hery, I applied the patch you provided to Tinman and myself. Improved, but there are three remaining compile errors on my platform.

Code: [Select]
../../code/graphics/gropenglshader.cpp:438: error: prototype for 'void opengl::shader::set_uniform(unsigned int, GLint)' does not match any in class 'opengl::shader'
../../code/graphics/gropenglshader.h:163: error: candidates are: void opengl::shader::set_uniform(unsigned int, float)
../../code/graphics/gropenglshader.h:157: error:                 void opengl::shader::set_uniform(unsigned int, int)

Was Tinman able to compile a clean build?

 
 

Offline Echelon9

  • 210
Re: MacOSX build process broken due to SVN 5694 commit
Thanks Tinman. My remaining compile issues with Hery's shader code may be platform specific; I'm using Xcode 2.5 on MacOS X 10.4.11 (PPC) while my primary development laptop is in for repairs.
« Last Edit: December 19, 2009, 03:40:29 am by Echelon9 »

 

Offline Hery

  • 26
Re: MacOSX build process broken due to SVN 5694 commit
This patch solves this problem. Let me know if there is still something else to fix.

[attachment deleted by admin]

 
 

Offline Echelon9

  • 210
Re: MacOSX build process broken due to SVN 5694 commit
Gah... I am having a frustrating time trying to apply this patch file (last time I had to make the changes manually).
Code: [Select]
$ patch -p0 -i ../gcc_macosx_fix.patch
(Stripping trailing CRs from patch.)
patching file code/graphics/gropenglshader.cpp
Hunk #1 FAILED at 250.
Hunk #2 FAILED at 313.
Hunk #3 FAILED at 381.
Hunk #4 FAILED at 425.
Hunk #5 FAILED at 475.
5 out of 5 hunks FAILED -- saving rejects to file code/graphics/gropenglshader.cpp.rej
(Stripping trailing CRs from patch.)
patching file code/graphics/gropenglshader.h
Hunk #1 FAILED at 154.
Hunk #2 FAILED at 204.
Hunk #3 FAILED at 214.
Hunk #4 FAILED at 233.
Hunk #5 FAILED at 325.
Hunk #6 FAILED at 334.
Hunk #7 FAILED at 344.
Hunk #8 FAILED at 353.
Hunk #9 FAILED at 383.
9 out of 9 hunks FAILED -- saving rejects to file code/graphics/gropenglshader.h.rej

It's not happening because I am trying to apply this to a working copy at a different revision to the patch, as both are 5726.
Code: [Select]
$ svn info
Path: .
URL: svn://svn.icculus.org/fs2open/trunk/fs2_open
Repository Root: svn://svn.icculus.org/fs2open
Repository UUID: 387891d4-d844-0410-90c0-e4c51a9137d3
Revision: 5726
Node Kind: directory
Schedule: normal
Last Changed Author: Sushi
Last Changed Rev: 5726
Last Changed Date: 2009-12-19 01:22:01 +0800 (Sat, 19 Dec 2009)
Properties Last Updated: 2009-12-14 17:03:41 +0800 (Mon, 14 Dec 2009)

$ head -n 4 ../gcc_macosx_fix.patch
Index: code/graphics/gropenglshader.cpp
===================================================================
--- code/graphics/gropenglshader.cpp    (revision 5726)
+++ code/graphics/gropenglshader.cpp    (working copy)

I've Google'd for newline and CRLF issues when using a Windows produced patch on OS X / Unix with no success with any of the suggested fixes, nor with --ignore-whitespaces or -Fn. Any help or suggestions?