Actually building 1.2.90 for Slackware current turned out not to be a
terrible pain at all - after translating the RPM spec file into a bash
script things went smoothly.
Using this build script on Xubuntu 12.04 was ok too. But alas Xvnc
there bailed out on start because of a keymap compile error or
On 5/17/13 2:01 PM, Brian Hinz wrote:
> I think I'm actually using a patch that you posted to the list sometime
> in Februaury(?). I wasn't able to build GnuTLS correctly on MinGW so
> I'm linking against the pre-compiled version listed in BUILDING.txt
Ah. OK, that's what I'm doing as well. Jus
On Fri, May 17, 2013 at 2:30 PM, DRC wrote:
> Brian,
>
> While we're on the subject, the Mac build has similar issues. It won't
> run on Mountain Lion:
>
> dyld: Library not loaded: /usr/local/lib/libintl.8.dylib
>Referenced from: /Applications/Network/TigerVNC Viewer
> 1.2.90.app/Contents/Ma
On Fri, May 17, 2013 at 2:06 PM, DRC wrote:
> Pursuant to our discussion on tigervnc-users regarding whether the
> project RPMs could be used on SuSE, I noticed that the RHEL 5 RPMs and
> the cross-compatible build have external dependencies on GnuTLS and
> libstdc++. That prevents them from trul
Brian,
While we're on the subject, the Mac build has similar issues. It won't
run on Mountain Lion:
dyld: Library not loaded: /usr/local/lib/libintl.8.dylib
Referenced from: /Applications/Network/TigerVNC Viewer
1.2.90.app/Contents/MacOS/TigerVNC Viewer
Reason: image not found
When I wa
Pursuant to our discussion on tigervnc-users regarding whether the
project RPMs could be used on SuSE, I noticed that the RHEL 5 RPMs and
the cross-compatible build have external dependencies on GnuTLS and
libstdc++. That prevents them from truly being cross-compatible. It
should be possible
