Hi Andre,and Seb, I will test it tonight.
If it’s OK I will need to have another round “take me by the hand” to learn how to build RT32 myself. I realize that I have to start with rawwiki, but if any additional directions are needed please write them here.
@sguyader : ok for informations but do you have an idea to provide gdb to end users?
@ilias_giarimis : thanks for testing master and gtk3 builds.
To set up the toolchain, simply follow step by step the rawpedia notice. Once the 1st build made, the more difficult part for me was to use basic git commands.
@gaaned92 I don’t know for a standalone gdb executable, but searching quickly on Google I found this gdb for windows with links for 32 and 64 bits versions. I haven’t tried, though. It just provides gdb.exe executable, I don’t know if there are any dependencies for running it.
Both release and debug builds crash at the start.
EDIT … both RawTherapee_WinXP_32_gtk3release_4.2.670.exe, and RawTherapee_WinXP_32_gtk3debug_4.2.670 are in fact release builds
Branch: gtk3
Version: 4.2.670
Changeset: 1a9121714a3a8e04d09ca0cf0f237345a732d962
Compiler: gcc 5.3.0
Processor: undefined
System: Windows
Bit depth: 32 bits
Gtkmm: V3.18.0
Build type: release
Build flags: -m32 -mthreads -mstackrealign -std=gnu++11 -march=native -Werror=unused-label -fopenmp -Werror=unknown-pragmas -mwindows -DNDEBUG -msse2 -mfpmath=sse -O3
Link flags: -m32 -mthreads -static-libgcc -static-libstdc++ -Wl,–large-address-aware,–verbose -march=native -mwindows -s -O3
OpenMP support: ON
MMAP support: ON
I have no time now nor experience with gdb so I leave the gdb report for later (I will need some help because last week I tried and failed )
@ilias_giarimis @sguyader
for debug build I had a bug ( faulty copy paste of windowsinno setup).
Regarding the Glib-Gio-Error : I just downloaded in Msys2 “mingw-w64-i686-gsettings-desktop-schemas”. Inside I find a gschemas.compiled that is much bigger than that provided in tentative bundle (36K vs 3K).
I am going to regenerate the install exe with it and upload in same google drive place. Done.
@sguyader : the gdb release 7.9 provided in your link can be shipped as is with rawtherapee. No dependency as ckecked with dependency walker. tested here on 32 bits.
@gaaned92 good to know for the shipable gdb. @Morgan_Hardwood, is it possible to ask everyone who is going to produce debug builds, to include the small gdb.exe in the bundle, and make reference to this in Rawpedia? This would probably help users providing good back traces without the hassle of installing MinGW.
Absolutely, and a good idea. Debug builds should include gdb.exe if possible. As I don’t use Windows and can’t verify the procedure, please ask adamreichold on GitHub to add it to RawPedia’s Windows article.
@Morgan_Hardwood should I open an issue at Github to ask adamreichold, or is there another way to send him a message through Github?
An issue is the best way.
@ilias_giarimis :
1- do you still get the error “setting schema… date-format”
2- I hope the bug regarding thumbnail construction is solved (that was an error in build parameters)
3 - The new gtk3 builds 4.2.672 are uploaded at the same place
Please could you test the GTK3 builds ?
RT_672 crashes at startup
Console messages … https://drive.google.com/file/d/0B0NqktTgc54sTlRUUmhpMHNTTGs/view?usp=sharing
@ilias_giarimis :
still a bug in innosetup. The “share” subdir got the name “lib”. So if you rename the “lib” subdirectory “share”, the access to Gsettings should be ok.
Sorry to take your time.
@gaaned92
Everything is fine after renaming “lib” to share, thanks.
RT starts normally and there is no problem with files without thumbs in cache.
When everything is in tact (innosetup script) I will give a try to compile RT_32bit myself 
@ilias_giarimis
good news. I fixed the innosetup file. The present problem with it is that we need a version for GTK2 an another for GTK3 branch as the share subdir is only needed for GTK3 and furthermore gdb.exe should be packed in bundle only for debug versions. nevertheless, to simplify, I modified the windowsinnosetup.iss.in in the repository to include all subdir (lib and share) and gdb.exe. I manually suppresses lines in the generated windowsinnosetup.iss when generating the installer. Hope I am clear.
I am uploading the GTK3 corrected installers at the same place.
Fine, thanks.
Since the GTK3_win32 builds are not compatible with WinXP32 … isn’t it better to
Hey, I’m not following the Windows compilation issues closely (i.e. disclaimer, I might be suggesting nonsense), but if you need to use two different InnoSetup scripts, one for 32-bit XP and one for 64-bit Vista and above, we can add both to the repository if that makes it easier for you.
@Morgan_Hardwood @sguyader the difference in the innoSetup scripts comes from the different subdir to install between gtk2 builds and gtk3 builds and if we want to include gdb.exe in the installer. For the moment, in order to simplify, the “innosetup.iss.in” that I modified can include some pointless subdir and files.
I think there are no differences between 32 bits and 64 bits scripts. Sebastien also has to modify manually the script depending of the branch.
It could be a good thing to automate completely the process in order to avoid error and minimize the size of application.
development build if you want to test
RawTherapee_WIN_32_gtk3-gui-touchup-and-bugfix release_4.2.675.exe available at My drive