BUG: osxvnc 2.2 requires 10.2.8 SDK

[michael.g.ross.98@…]

osxvnc fails to build on dual G5, Mac OS X 10.4.9, output below

athena:/Users/mgross admin$ sudo port install osxvnc
Password:
--->  Fetching osxvnc
--->  Verifying checksum(s) for osxvnc
--->  Extracting osxvnc
--->  Applying patches to osxvnc
--->  Configuring osxvnc
--->  Building osxvnc
Error: Target com.apple.build returned: shell command "cd "/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_aqua_osxvnc/work/OSXvnc" && xcodebuild  -alltargets -configuration Deployment build OBJROOT=build/ SYMROOT=build/ " returned error 1
Command output: === BUILDING NATIVE TARGET jpg WITH CONFIGURATION Deployment ===

Checking Dependencies...
error: There is no SDK at specified SDKROOT_ppc path '/Developer/SDKs/MacOSX10.2.8.sdk'
** BUILD FAILED **

Error: Status 1 encountered during processing.
athena:/Users/mgross admin$ 

[markd@…]

Please include version in summary -I changed it. Assign to maintainer.

[ryandesign@…]

Michael: Please install the Mac OS X 10.2.8 SDK from the Xcode disk image. It's not installed by default.

I'll leave this bug open, as I would like to ideally remove the requirement of the 10.2.8 SDK from this installation. But it will take some work, and is not a priority for me at this time. However, if someone else would like to discover how to do this and attach a patch to this ticket, I will of course evaluate it.

[ryandesign@…]

Priority is low, because there's an easy workaround (install the 10.2.8 SDK). Still, I would like to change it so the 10.2.8 SDK isn't required, since MacPorts only officially supports 10.3 and up.

The issue remains with osxvnc 2.2.

[anton@…]

I suggest increasing priority on this bug as the 10.2.8 SDK is not available in XCode 3.0 and thus this package will not build on Leopard

[anton@…]

I forgot to mention that this bug still bites you when building on an Intel Mac with variant -universal. Why is it trying to build PPC when deselecting universal? I would expect -universal to build an Intel only binary as it does with other packages and thus negate the need for the PPC only SDK. Perhaps that should be a separate ticket, however.

[ryandesign@…]

osxvnc always builds universal. The +universal variant was added to indicate that this is the case. Using "-universal" is not supported. If you would like a non-universal build of osxvnc, please do file a new ticket. Cc nox@macports on that ticket because he has experience with making default-universal software build non-universal.

If 10.2.8 SDK is not available on Leopard, then osxvnc does not build on Leopard, regardless of whether using MacPorts or not, and you should file a ticket with the developers of osxvnc.

[michael.g.ross.98@…]

Is this package necessary in Leopard? The Screen Sharing feature appears to offer superior features. If it allows non-Apple VNC clients to connect (and I don't know if it does or not), then perhaps maintaining OSXvnc is not worth the effort.

[anton@…]

In some cases, the features are indeed superior in Leopard's built in VNC server. I can get slightly faster frame refreshes with it, and it works by simply setting Remote Management on in the Sharing preference pane. I have tested it with cotvnc and it works well. However, it is less than obvious to many users how to force Screen Sharing to require SSH, while it's a simple check box in Vine Server (osxvnc)

[ryandesign@…]

Greg Kolanek also reported this issue to me via email.

The solution will be to update Vine Server to 3.0, which requires Tiger. See ticket #13803.

[ryandesign@…]

I wasn't quite right: 3.0 requires Panther. Still, that means it shouldn't use the 10.2.8 SDK anymore. So this is now fixed as of r33415.