|
Compiling
How to compile and install VMware View Open Client from source.
Featured Our binary packages should work on most Linux and Mac systems, but if you prefer to build from source, these instructions may help you. They were tested on 32-bit Ubuntu 8.10 and Mac OS X 10.5. Development EnvironmentYou'll need a compiler, toolchain, and development packages for the libraries we use, and the latest source release. LinuxMost dependencies should be available as binary packages from your distribution, either on your install media or from your package repository. On Ubuntu, you can install the build-essentials meta-package to get most of what you need. Mac OS XYou need Mac OS X 10.5 above, with the developer tools installed. We use a few additional pieces of software not included with OS X, and recommend getting them from MacPorts. Library Requirements
Open IssuesBefore building the client, please check the list of open issues for patches you may need to build on your platform. CompilingVMware View Open Client uses GNU Autoconf and GNU Automake. For details on how to build software using these tools, see the included INSTALL file. LinuxA few simple commands should be all you need to need to get started: $ tar zxf VMware-view-open-client-source-*.tar.gz $ cd VMware-view-open-client-source-* $ ./configure && make Your configure command may vary depending on your environment; for example, to build on 64-bi Fedora, you may need to do this instead: $ ./configure --with-boost-libdir=/usr/lib64 && make You can then start the client by running: $ ./vmware-view To install the client, just run make install: $ sudo make install This will install binaries in /usr/bin and documentation in /usr/share/doc/VMware-view-open-client/. You can also run make debs or make rpms to build binary packages. Mac OS XThe steps to build and run the Mac OS client are similar: $ tar zxf VMware-view-open-client-source-*.tar.gz $ cd VMware-view-open-client-source-* $ PKG_CONFIG_PATH=/opt/local/lib/pkgconfig:/usr/lib/pkgconfig CPPFLAGS="-I/opt/local/include" LIBS="-L/opt/local/lib" ./configure && make You can then start the client by opening your build directory in Finder, and double clicking the VMware View Open Client application. Drag this to your Applications folder to install. You can also run make dmg to build a disk image suitable for distribution. | ||||||||||||||||||||||||||||||||
► Sign in to add a comment
To get this to work on Ubuntu 8.04 you have to compile intltool >=0.21 from source. I just took the source intltool from intrepid https://launchpad.net/ubuntu/intrepid/+source/intltool/0.40.5-0ubuntu1 and compiled it after installing the listed compile-time dependencies. Hope this helps every one else sticking with the LTS.
Anyone has experience compiling this baby for ARM? Any suggestion/hint is really appreciated.
On Linux 2.6.25 (custom distro) I get the fatal error in Make
I have checked the tarball on two different systems and they both have the file, but it is missing the trailing 'b' (i.e., designable.ni). Is there a flag for ignoring the OSX bits?
Is this from the tarball on the download site, or did you change something?
That sounds like tar V7 format, which limits files to 99 characters. We're supposed to be using pax which does not have this limit, however, things like busybox may not support that yet.
In any case, you could:
a) rename the .ni file .nib b) touch the .nib c) make -k
hi. i compiled client from source and got a problem trying to connect to virtual machine:
Relative or system path /home/arch/vmware/VMware-view-open-client-source-4.0.0-215529/vmware-view-usb does not exist. /usr/bin/vmware-view-usb was not found; disabling USB redirection. rdesktop(27637) died. rdesktop(27637) exited with status: 1
OS debian lenny //on openSuse binaries installed from rpm work perfectly
Good morning, are there any instructions on how compile this for a SLETC system?
Thanks!
If you want to use it on a SLETC system I suggest the SLETC add-on that we build.
You can build this add-on yourself by doing 'make rpms'; this will generate the -lite.rpm used by SLETC.
I've used the rpms option while making, however I recieve a missing library error when running on the SLETC. libboost_signals-gcc41-1_34_1.so.1.34.1 I'm compiling it myself in order to change a parameter sent to the rdesktop that we don't want.
try building boost with dynamic libraries disabled.
I may have gotten past that, now i am receiving a missing library error for libicuuc.so.44. i try compiling with --enable-static-icu but that errors out not being able to find uidna_IDNToASCII. I've configured icu with the --enable-static argument, and have installed it that way. but if i disable shared i'm not even able to compile the normal version of the openview client. Is there some way to know where icu is putting its static libraries, and then pointing the compile of the VM to that location? Thanks
I think I've got it. It had to do with using too new of versions of icu, and gtk.
I'm having the same problem as wagnet.452 had with regards to libboost_signals failing when I try to deploy. My question is I'm not sure how to build boost with dynamic libraries disabled.
My assumption is its somehow within the ./configure XXoptionXX
It seems that the Boost.Signals version should be at minimum 1.34.1. Then I download several Boost.Signals 1.34.1 libraries and must try to generate dynamic library.But how do I cross-compile the boost.signals into dynamic libraries that is proper for st40?
I try to install on my freeBSD 8.1 Release with KDE, but getting this problem:
# tar zxf VMware-view-open-client-source-4.5.0-297975.tar.gz
# cd VMware-view-open-client-source-4.5.0-297975
# ./configure && make Configuring VMware-view-open-client 4.5.0-297975 checking build system type... i386-unknown-freebsd8.1 checking host system type... i386-unknown-freebsd8.1 checking which interface to build... Gtk+ checking for pkg-config... /usr/local/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for GLIB... yes checking for GTK... yes checking for XML... yes checking for CURL... yes checking for SSL... gnome-config: not found configure: error: Package requirements (openssl >= 0.9.8) were not met:
No package 'openssl' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix.
Alternatively, you may set the environment variables SSL_CFLAGS and SSL_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details.
Trying to compile on ARM processor, exiting with the following error. Has anyone successfully done this? not sure what thumb mode even is? /tmp/cc1w6ryL.s:2078: Error: selected processor does not support Thumb mode `swp r0,r5,r6?'
make: all? Error 2
same question with ARM processor. Anybody want to help?
Hi, i'm a mandriva distro maintainer and i prepare patches for Werror-security policy
http://pastie.org/2969655
Hello community, working on PCOIP for ARM (wyse t50 linux embedded) cross compiling from squeeze, can't figure out the result of this command :
./configure --target=arm-linux-gnueabi --host=arm-linux-gnueabi --prefix=/home/user/edev/vmware-client --with-boost-signals=no
Result : checking for uidna_IDNToASCII in -licuuc... no configure: error: libicu is required, but not found. Check config.log for details.
'Think Wagner could help thanks to everyone.