Best Method for Windows Builds

[Ben Mathews]

Is there a procedure for reproducing the Windows builds on Bintray?

I've tried various methods of building TigerVNC and have not yet been able to build something that works.
 * MXE on Ubuntu 18.04
 * mingw on Windows 10
 * mingw-w64 on Windows 10

In all cases I had to modify StaticBuild.cmake to add linking to pthread, winpthread, nettle, idn2, unistring, and p11-kit, and in all cases the resulting executable segfaults after the first client disconnects.  I've also tried building various releases, but that has not had any effect.

What is the best way to compile TigerVNC for Windows?  I am willing to tailor my build approach to use known-working methods, but need to know what those are.

Thanks in advance!

Ben

[Levi Stanley]

Not sure if this is the standard way.  I download msys2 (https://www.msys2.org/), and I install cmake for windows here (https://cmake.org).

I make sure cmake is in my path, and when I first run it, it complains about the date, and it can't find the c or c++ compilers, I install them using msys2 in the msys2 terminal using pacman.  After cmake-gui (use cmake-gui it will find all your libraries for you and tell you what you need pacman to install), stops complaining, I use mingw-make and see how far it gets, and solve any problems that arise.

--
You received this message because you are subscribed to the Google Groups "TigerVNC Developer Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tigervnc-deve...@googlegroups.com.
To post to this group, send email to tigervn...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tigervnc-devel/9940cf5d-ff7a-48cd-9086-b03f04e8f813%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ben Mathews]

When I try using the native Windows cmake executable (rather than the msys2 one), I am unable to run the CMakeTestCCompiler module.  It doesn't appear to be able to create the temporary files to run the try_compile() function. 

When I run cmake from within msys2 and run make from in there, I run into the same issues as before: linking fails unless I add stuff to StaticBuild.cmake, and after I do that, the resulting executable segfaults after the first client disconnects.

Ben

On Saturday, May 18, 2019 at 12:40:07 AM UTC-6, Levi Stanley wrote:

Not sure if this is the standard way.  I download msys2 (https://www.msys2.org/), and I install cmake for windows here (https://cmake.org).

I make sure cmake is in my path, and when I first run it, it complains about the date, and it can't find the c or c++ compilers, I install them using msys2 in the msys2 terminal using pacman.  After cmake-gui (use cmake-gui it will find all your libraries for you and tell you what you need pacman to install), stops complaining, I use mingw-make and see how far it gets, and solve any problems that arise.

On Fri, May 17, 2019 at 11:15 PM Ben Mathews <benjamin...@gmail.com> wrote:

Is there a procedure for reproducing the Windows builds on Bintray?

I've tried various methods of building TigerVNC and have not yet been able to build something that works.
 * MXE on Ubuntu 18.04
 * mingw on Windows 10
 * mingw-w64 on Windows 10

In all cases I had to modify StaticBuild.cmake to add linking to pthread, winpthread, nettle, idn2, unistring, and p11-kit, and in all cases the resulting executable segfaults after the first client disconnects.  I've also tried building various releases, but that has not had any effect.

What is the best way to compile TigerVNC for Windows?  I am willing to tailor my build approach to use known-working methods, but need to know what those are.

Thanks in advance!

Ben

--
You received this message because you are subscribed to the Google Groups "TigerVNC Developer Discussion" group.

To unsubscribe from this group and stop receiving emails from it, send an email to tigervn...@googlegroups.com.

[Brian Hinz]

I build the official binaries with mxe on CentOS 7.  I don’t recall having to make any modifications to the mxe source code at all.  Give me a bit and I’ll try to send you the exact recipe that I use.

-brian

To unsubscribe from this group and stop receiving emails from it, send an email to tigervnc-deve...@googlegroups.com.

To post to this group, send email to tigervn...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/tigervnc-devel/46621415-8af6-4f74-9a4b-ef836d87030a%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Sent from Gmail Mobile

[Brian Hinz]

I guess I have to correct myself...  I apply one small patch to the tigervnc source in order to get it to link correctly under mxe:

--- a/cmake/StaticBuild.cmake   2018-08-05 21:36:31.105856377 -0400

+++ b/cmake/StaticBuild.cmake   2018-08-05 21:35:58.949853394 -0400

@@ -26,7 +26,7 @@

   # gettext is included in libc on many unix systems

   if(NOT LIBC_HAS_DGETTEXT)

-    set(GETTEXT_LIBRARIES "-Wl,-Bstatic -lintl -liconv -Wl,-Bdynamic")

+    set(GETTEXT_LIBRARIES "-Wl,-Bstatic -lidn2 -lintl -lunistring -liconv -Wl,-Bdynamic")

   endif()

   if(GNUTLS_FOUND)

I also invoke cmake specifically as /opt/mxe/usr/bin/x86_64-w64-mingw32.static-cmake.  

[Ben Mathews]

Thanks Brian.  When I try that using MXE on Ubuntu 18.04, linking vncconfig.exe fails with complains about undefined references to clock_gettime, nettle, pthread, and other things.  Same issue I run into when trying to compile in other frameworks.  I've worked around this in the past by adding these dependencies into the StaticBuild.cmake file, but always end up with an executable that segfaults.  I will try tomorrow w/ mxe in a Fedora VM.

BTW, the way I call cmake is:

x86_64-w64-mingw32.static-cmake -DCMAKE_SYSTEM_NAME=Windows -DCMAKE_TOOLCHAIN_FILE=~/mxe/usr/x86_64-w64-mingw32.static/share/cmake/mxe-conf.cmake -DBUILD_STATIC=1 ../

On Saturday, May 18, 2019 at 9:45:20 PM UTC-6, Brian Hinz wrote:

I guess I have to correct myself...  I apply one small patch to the tigervnc source in order to get it to link correctly under mxe:

--- a/cmake/StaticBuild.cmake   2018-08-05 21:36:31.105856377 -0400

+++ b/cmake/StaticBuild.cmake   2018-08-05 21:35:58.949853394 -0400

@@ -26,7 +26,7 @@

   # gettext is included in libc on many unix systems

   if(NOT LIBC_HAS_DGETTEXT)

-    set(GETTEXT_LIBRARIES "-Wl,-Bstatic -lintl -liconv -Wl,-Bdynamic")

+    set(GETTEXT_LIBRARIES "-Wl,-Bstatic -lidn2 -lintl -lunistring -liconv -Wl,-Bdynamic")

   endif()

   if(GNUTLS_FOUND)

I also invoke cmake specifically as /opt/mxe/usr/bin/x86_64-w64-mingw32.static-cmake.  

On Sat, May 18, 2019 at 8:50 PM Brian Hinz <bph...@users.sourceforge.net> wrote:

I build the official binaries with mxe on CentOS 7.  I don’t recall having to make any modifications to the mxe source code at all.  Give me a bit and I’ll try to send you the exact recipe that I use.

-brian

To view this discussion on the web visit https://groups.google.com/d/msgid/tigervnc-devel/46621415-8af6-4f74-9a4b-ef836d87030a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ben Mathews]

I tried again but in Fedora. 

Starting with a clean Fedora Workstation 30-1.2 install, I installed MXE with:

sudo yum install autoconf automake bash bison bzip2 flex gcc-c++ gdk-pixbuf2-devel gettext git gperf intltool libtool lzip make openssl-devel p7zip patch perl pkgconfig python ruby sed unzip wget xz
git clone https://github.com/mxe/mxe.git
cd mxe/
make MXE_TARGETS='x86_64-w64-mingw32.static' cmake gcc
make MXE_TARGETS='x86_64-w64-mingw32.static' zlib fltk gnutls gettext libjpeg-turbo

Then try and build tigervnc with:

git clone https://github.com/TigerVNC/tigervnc.git
cd tigervnc/
git checkout v1.9.0
mkdir build
cd build/
export PATH=$PATH:/home/ben/mxe/usr/bin
x86_64-w64-mingw32.static-cmake -DCMAKE_SYSTEM_NAME=Windows -DCMAKE_TOOLCHAIN_FILE=/home/ben/mxe/usr/x86_64-w64-mingw32.static/share/cmake/mxe-conf.cmake -DBUILD_STATIC=1 ../
make

On the first run of that I get:

/home/ben/mxe/usr/bin/x86_64-w64-mingw32.static-ld: cannot find -lgcc_eh

Apparently static builds of libgcc in mxe don't include libgcc_eh?  If I either modify StaticBuild.cmake to not link to that, or make a symlink from libgcc to libgcc_eh, it fails in exactly the same way as before on Ubuntu.

[ 65%] Linking CXX executable vncconfig.exe
/home/ben/mxe/usr/lib/gcc/x86_64-w64-mingw32.static/5.5.0/../../../../x86_64-w64-mingw32.static/lib/../lib/libgnutls.a(system.o): In function `_gnutls_gettime':
/home/ben/mxe/tmp-gnutls-x86_64-w64-mingw32.static/gnutls-3.6.6/lib/system.c:54: undefined reference to `clock_gettime'
/home/ben/mxe/usr/lib/gcc/x86_64-w64-mingw32.static/5.5.0/../../../../x86_64-w64-mingw32.static/lib/../lib/libhogweed.a(pkcs1-sec-decrypt.o): In function `_nettle_pkcs1_sec_decrypt':
/home/ben/mxe/tmp-nettle-x86_64-w64-mingw32.static/nettle-3.4.1/pkcs1-sec-decrypt.c:81: undefined reference to `nettle_cnd_memcpy'
/home/ben/mxe/usr/lib/gcc/x86_64-w64-mingw32.static/5.5.0/../../../../x86_64-w64-mingw32.static/lib/../lib/libhogweed.a(pkcs1-sec-decrypt.o): In function `_nettle_pkcs1_sec_decrypt_variable':
/home/ben/mxe/tmp-nettle-x86_64-w64-mingw32.static/nettle-3.4.1/pkcs1-sec-decrypt.c:134: undefined reference to `nettle_cnd_memcpy'
/home/ben/mxe/tmp-nettle-x86_64-w64-mingw32.static/nettle-3.4.1/pkcs1-sec-decrypt.c:142: undefined reference to `nettle_cnd_memcpy'
/home/ben/mxe/usr/lib/gcc/x86_64-w64-mingw32.static/5.5.0/libstdc++.a(eh_globals.o):(.text$__tcf_0+0x17): undefined reference to `pthread_key_delete'
/home/ben/mxe/usr/lib/gcc/x86_64-w64-mingw32.static/5.5.0/libstdc++.a(eh_globals.o):(.text$__cxa_get_globals_fast+0x27): undefined reference to `pthread_getspecific'
/home/ben/mxe/usr/lib/gcc/x86_64-w64-mingw32.static/5.5.0/libstdc++.a(eh_globals.o):(.text$__cxa_get_globals+0x27): undefined reference to `pthread_getspecific

...

/home/ben/mxe/tmp-gcc-x86_64-w64-mingw32.static/gcc-5.5.0.build_/x86_64-w64-mingw32.static/libgcc/./gthr-default.h:725: undefined reference to `pthread_setspecific'
/home/ben/mxe/tmp-gcc-x86_64-w64-mingw32.static/gcc-5.5.0.build_/x86_64-w64-mingw32.static/libgcc/./gthr-default.h:725: undefined reference to `pthread_setspecific'
collect2: error: ld returned 1 exit status
make[2]: *** [win/vncconfig/CMakeFiles/vncconfig.dir/build.make:176: win/vncconfig/vncconfig.exe] Error 1
make[1]: *** [CMakeFiles/Makefile2:547: win/vncconfig/CMakeFiles/vncconfig.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

Do you see anything else I might be doing differently than you?  I notice you install mxe to /opt, but I don't think that should make a difference.

Thanks in advance,

Ben

On Saturday, May 18, 2019 at 9:45:20 PM UTC-6, Brian Hinz wrote:

I guess I have to correct myself...  I apply one small patch to the tigervnc source in order to get it to link correctly under mxe:

--- a/cmake/StaticBuild.cmake   2018-08-05 21:36:31.105856377 -0400

+++ b/cmake/StaticBuild.cmake   2018-08-05 21:35:58.949853394 -0400

@@ -26,7 +26,7 @@

   # gettext is included in libc on many unix systems

   if(NOT LIBC_HAS_DGETTEXT)

-    set(GETTEXT_LIBRARIES "-Wl,-Bstatic -lintl -liconv -Wl,-Bdynamic")

+    set(GETTEXT_LIBRARIES "-Wl,-Bstatic -lidn2 -lintl -lunistring -liconv -Wl,-Bdynamic")

   endif()

   if(GNUTLS_FOUND)

I also invoke cmake specifically as /opt/mxe/usr/bin/x86_64-w64-mingw32.static-cmake.  

On Sat, May 18, 2019 at 8:50 PM Brian Hinz <bph...@users.sourceforge.net> wrote:

I build the official binaries with mxe on CentOS 7.  I don’t recall having to make any modifications to the mxe source code at all.  Give me a bit and I’ll try to send you the exact recipe that I use.

-brian

To view this discussion on the web visit https://groups.google.com/d/msgid/tigervnc-devel/46621415-8af6-4f74-9a4b-ef836d87030a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Levi Stanley]

I made sure cmake was in my path, and I issued cmake-gui in the msys2 terminal window.  It opens to initially to a window like the screenshot below, however initally it ask you questions about the type of make you are doing, and then you press configure, after you get it set, click generate.  I initially get an error on the timestamp, I hardcode that, and then run configure again, it says the compilers are not in path, I install them via pacman, and finally I end up adding in -lpthread and adding in some other paths to include and I run make until it finally finishes at 100%.

I use cmake for windows because the cmake-gui believe was crashing, and rather deal with that I found that cmake for windows actually worked.

Which version of tigervnc are you attempting to create?  I can probably download and go the branch you are using and see if I have the same issue.

Best regards,

Levi

To unsubscribe from this group and stop receiving emails from it, send an email to tigervnc-deve...@googlegroups.com.

To post to this group, send email to tigervn...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/tigervnc-devel/46621415-8af6-4f74-9a4b-ef836d87030a%40googlegroups.com.

[Brian Hinz]

I know that you are passing MXE_TARGETS on the command line, but here's what I have in settings.mk:

MXE_TARGETS := i686-w64-mingw32.static x86_64-w64-mingw32.static

To view this discussion on the web visit https://groups.google.com/d/msgid/tigervnc-devel/CAGhvLC1JoWOJC5a5mWj_7aGvKqfHsoicD26zS02oi8bzconB6Q%40mail.gmail.com.

[Ben Mathews]

Brian, I am back on this and still unable to compile TigerVNC.  In attempt to be as get to the build environment that you referenced, I am using mxe on Centos 7.  I started with a base Centos install, and did a minimal install of dependencies to build and compile mxe.  I then make the change you referenced to StaticBuild.cmake, and still get errors when building. 

[ 65%] Linking CXX executable vncconfig.exe

/opt/mxe/usr/bin/x86_64-w64-mingw32.static-ld: cannot find -lgcc_eh
/opt/mxe/usr/bin/x86_64-w64-mingw32.static-ld: cannot find -lgcc_eh

collect2: error: ld returned 1 exit status

make[2]: *** [win/vncconfig/vncconfig.exe] Error 1
make[1]: *** [win/vncconfig/CMakeFiles/vncconfig.dir/all] Error 2
make: *** [all] Error 2

Do you make any other changes to your host OS, MXE build environment, or TigerVNC source to get it to compile the Windows binaries?  What arguments to you pass to cmake?  Any other differences you can think of?

Thanks!

Ben

On Sunday, May 19, 2019 at 9:52:32 PM UTC-6, Brian Hinz wrote:

I know that you are passing MXE_TARGETS on the command line, but here's what I have in settings.mk:

MXE_TARGETS := i686-w64-mingw32.static x86_64-w64-mingw32.static

On Sun, May 19, 2019 at 4:41 PM Levi Stanley <le...@eneservices.com> wrote:

I made sure cmake was in my path, and I issued cmake-gui in the msys2 terminal window.  It opens to initially to a window like the screenshot below, however initally it ask you questions about the type of make you are doing, and then you press configure, after you get it set, click generate.  I initially get an error on the timestamp, I hardcode that, and then run configure again, it says the compilers are not in path, I install them via pacman, and finally I end up adding in -lpthread and adding in some other paths to include and I run make until it finally finishes at 100%.

I use cmake for windows because the cmake-gui believe was crashing, and rather deal with that I found that cmake for windows actually worked.

Which version of tigervnc are you attempting to create?  I can probably download and go the branch you are using and see if I have the same issue.

Best regards,

Levi

To view this discussion on the web visit https://groups.google.com/d/msgid/tigervnc-devel/46621415-8af6-4f74-9a4b-ef836d87030a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "TigerVNC Developer Discussion" group.

To unsubscribe from this group and stop receiving emails from it, send an email to tigervn...@googlegroups.com.
To post to this group, send email to tigervn...@googlegroups.com.