The goal of a cross-compatible build isn't necessarily to eliminate all
dependencies but to eliminate dependencies that aren't forward ABI compatible
with the platform on which you build or which might not be readily available. I
would say that the goal should be to produce similar dependencies to TigerVNC
1.2. My build scripts for TigerVNC 1.2 are in the SVN repo. Why can't you
reference those?
On Jun 21, 2013, at 7:28 AM, Brian Hinz <bph...@users.sourceforge.net> wrote:
> On Fri, Jun 21, 2013 at 8:38 AM, D.L.C. Burggraaff <burd...@gmail.com> wrote:
>> Yes, when I issued "replace" in an xterm I got the hint that replace was
>> included in the mysql-server package. However, a mysql build dependency did
>> not seem "right" to me.
>> So now I installed mysql-server (with a slew of dependencies) and via the
>> replace man page could analyze the pack_tiger.sh line 18.I replaced (sic) it
>> by a 'sed -i -e "s/Xvnc/Xtigervnc/g" usr/bin/tigervncserver' command.
>> Following the instructions as given previously the .deb was created ok.
>> Double clicking on the deb produced a "The package is of bad quality. The
>> package doesn't provide a valid Installed-Size control field. See Debian
>> Policy 5.6.20" popup, Pressing "Ignore and install" made the package install
>> nevertheless.
>> Running "vncserver :60" and "vncviewer localhost:60 &" was ok.
>> As an aside, the /usr/share/vnc/classes/* files were not renamed and
>> therefore may collide with an other VNC alternative.
>> Kind regards, Dick
>>
>>
>>
>> On Thu, Jun 20, 2013 at 3:18 PM, Robert Goley <rago...@rdasys.com> wrote:
>>> The replace utility is part of the mysql server package. It is a handy
>>> string replacement tool.
>>>
> Just FYI, I don't mind incorporating this into the nightly build script,
> especially if you guys continue to provide guidance with the deb files. I've
> been trying to eliminate that libexpat dependency, but so far haven't managed
> to do so successfully. In theory, many of the dependencies on shared
> libraries could be eliminated from the vnc* binaries (vncviewer, vncpasswd,
> etc.) by linking against the static versions that I already have to build to
> link Xvnc against, but I'm having trouble getting the linker to pick them up.
> I suppose that the CMake files might need to be hacked a bit in order to
> make that happen cleanly...
>
> -brian
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Tigervnc-devel mailing list
> Tigervnc-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
