Menu
▾
▴
linuxsampler-devel
|
From: Christian S. <sch...@li...> - 2016-09-25 17:00:45
|
Hi Windows users, I just updated the cross compilers for the Windows platform on our build server. One of them had an ancient old version which I got tired of dealing with on source code level. In case you encounter any issues with the new LinuxSampler Windows installer version from today (linuxsampler_20160925_setup.exe) or later, then just let me know! CU Christian |
|
From: Andreas P. <and...@ou...> - 2016-09-26 18:01:23
|
Christian Schoenebeck wrote: > In case you encounter any issues with the new LinuxSampler Windows installer > version from today (linuxsampler_20160925_setup.exe) or later, then just let > me know! The 32 bit programs are now broken, as the gcc and stdc++ dll files are missing in the installer. /Andreas |
|
From: Andreas P. <and...@ou...> - 2016-09-26 18:30:37
|
Andreas Persson wrote: > Christian Schoenebeck wrote: >> In case you encounter any issues with the new LinuxSampler Windows installer >> version from today (linuxsampler_20160925_setup.exe) or later, then just let >> me know! > The 32 bit programs are now broken, as the gcc and stdc++ dll files are > missing in the installer. I tried to copy the dll files from the build server (/usr/lib/gcc/i686-w64-mingw32/4.9-win32), and then linuxsampler.exe starts without errors, but neither gigedit nor qsampler work. I think we must find or build new versions of the Qt and gtkmm libs compatible with the newer gcc. The 64 bit version of gigedit however seems to work fine. /Andreas |
|
From: Christian S. <sch...@li...> - 2016-09-26 18:43:45
|
On Monday, September 26, 2016 18:30:21 Andreas Persson wrote: > I tried to copy the dll files from the build server > (/usr/lib/gcc/i686-w64-mingw32/4.9-win32), and then linuxsampler.exe > starts without errors, but neither gigedit nor qsampler work. I think we > must find or build new versions of the Qt and gtkmm libs compatible with > the newer gcc. I was actually currently trying another approach, I was playing on the libgig-win32 target and added "-static-libgcc -static-libstdc++" and removed "--disable-static". It builds fine but fails when it tries to link one of the command line tools, because some of the static symbols are now tried to be included to both the libgig DLLs as well as the command line applications. I give up for today. Maybe tomorrow ... CU Christian |
|
From: Christian S. <sch...@li...> - 2016-10-03 15:40:35
|
On Monday, September 26, 2016 20:44:17 Christian Schoenebeck wrote: > On Monday, September 26, 2016 18:30:21 Andreas Persson wrote: > > I tried to copy the dll files from the build server > > (/usr/lib/gcc/i686-w64-mingw32/4.9-win32), and then linuxsampler.exe > > starts without errors, but neither gigedit nor qsampler work. I think we > > must find or build new versions of the Qt and gtkmm libs compatible with > > the newer gcc. > > I was actually currently trying another approach, I was playing on the > libgig-win32 target and added "-static-libgcc -static-libstdc++" and removed > "--disable-static". It builds fine but fails when it tries to link one of > the command line tools, because some of the static symbols are now tried to > be included to both the libgig DLLs as well as the command line > applications. > > I give up for today. Maybe tomorrow ... I had a look at compiling a new GTKMM version for the 32-bit Windows build server today, however GTKMM requires such a huge crap chain of library dependencies that it would take ages to compile all of them. Total horror show! Did I mention before how much I regret not having switched to Qt for gigedit somewhere in the past? *grrrr* How about compltely dropping support for 32 bit Windows machines with our installer? I mean is anybody still using a 32 bit Windows machine actually? My guess is that there is almost nobody still using a 32 bit Windows system, and if so, then there are probably more useful things to spend my time on. CU Christian |
|
From: Andreas P. <and...@ou...> - 2016-10-09 19:56:11
|
Christian Schoenebeck wrote: > On Monday, September 26, 2016 20:44:17 Christian Schoenebeck wrote: >> On Monday, September 26, 2016 18:30:21 Andreas Persson wrote: >>> I tried to copy the dll files from the build server >>> (/usr/lib/gcc/i686-w64-mingw32/4.9-win32), and then linuxsampler.exe >>> starts without errors, but neither gigedit nor qsampler work. I think we >>> must find or build new versions of the Qt and gtkmm libs compatible with >>> the newer gcc. >> >> I was actually currently trying another approach, I was playing on the >> libgig-win32 target and added "-static-libgcc -static-libstdc++" and removed >> "--disable-static". It builds fine but fails when it tries to link one of >> the command line tools, because some of the static symbols are now tried to >> be included to both the libgig DLLs as well as the command line >> applications. >> >> I give up for today. Maybe tomorrow ... > > I had a look at compiling a new GTKMM version for the 32-bit Windows build > server today, however GTKMM requires such a huge crap chain of library > dependencies that it would take ages to compile all of them. Total horror > show! Did I mention before how much I regret not having switched to Qt for > gigedit somewhere in the past? *grrrr* > Just so you know, I'm working on this now. My plan is to use prebuilt dll files from the msys2 project. This means I have to use a newer compiler than the one provided by Debian. The compiler is installed and used on the build server for win 32 bit, but I haven't finished the changes in the installer scripts yet. /Andreas |
|
From: Christian S. <sch...@li...> - 2016-10-09 20:30:04
|
On Sunday, October 09, 2016 19:55:54 Andreas Persson wrote: > Just so you know, I'm working on this now. My plan is to use prebuilt > dll files from the msys2 project. This means I have to use a newer > compiler than the one provided by Debian. The compiler is installed and > used on the build server for win 32 bit, but I haven't finished the > changes in the installer scripts yet. That's timing. I was already starting to abandon the 32 bit Windows build by updating the Windows installer. So I guess I am not committing that. ;-) Thanks for letting me know! CU Christian |
Thanks for helping keep SourceForge clean.
X