@damarko Native builds use all the features of your CPU, while generic builds can’t do that (because they have to work on all CPUs which are supported by the build), Means if your CPU for example supports SSE4, AVX and FMA, the generic build will only support SSE2, whole your native build will support also SSE4, AVX and FMA.
Ingo, that is the reason I decided to compile. I red this forum for some time and concluded it would be best to have the software that would be adopted to my system specifications, although I am not very skillful in doing such things.
What amazes me is that when I turn on my machine, or restart it, RT opens in few seconds. Later, when windows load its stuff, opening time reaches 30 seconds. It is not so big problem for me, but I really consider installing linux alongside.
That’s a good reason
At this time, do you have enough memory available? I don’t observe this behaviour on my W10 machine (16GB)
I have 8 GB of memory, Intel I5 processor, ssd hd… not a beast, but I think there should be no problem?
I also whitelisted RT folder in antivirus and antispyware software, deactivated floppy in bios…
Have you inserted (and optionally removed) any memory cards, network drives, other mass storage devices, etc?
I have external hd inserted.
And if you don’t insert the external HD after booting Windows, and if you don’t use any programs which can create new “devices”, does the startup time still go from 5s to 30s?
Now I removed external hd, restarted computer and tried… no big difference… just after booting into windows program opens in a few seconds, after approximately one minute opening time is about 25 sec.
Thank you for your efforts but you don’t have to waste your time with this. It’s obviously something in my comp setup that is preventing RT from loading faster, but I can live with that. Just one more sip of coffee 
When I test here, the above icons do not seem missing. Do you notice this bug with one of my own build?
Nevertheless I will add it.
If I remember, it was @TooWaBoo who gave me this list.
When deleting the cursors, nothing seems changed. I have to test further.
Does’nt seem required
But do you think it should be documented?
@gaaned92
The cursor I gave you look better than the originales. e.g. a fine crosshair for curves and identical arrows for all crop directions.
I agree, but in order everybody can include them in builds, should it be possible to ship those cursors with rawtherapee and perhaps install them ?
Simple answer, Yes. 
Question:
Please, can you tell me the time of the day?
Answer:
Yes
And can you do that?
If I don’t include cursors and Gdk-pixbuf, I get warning at run time
Andre@C1 MINGW64 /d/RAWTHERAPEE/5.3-482-gf644d41f
$ ./rawtherapee
(rawtherapee.exe:23432): Gdk-WARNING **: Failed to load cursor theme Adwaita
(rawtherapee.exe:23432): Gtk-WARNING **: Could not load a pixbuf from /org/gtk/libgtk/theme/Adwaita/assets/check-symbolic.svg.
This may indicate that pixbuf loaders or the mime database could not be found.
So I think it is better keep those items included.
The list of dependencies should be as follows (until cursors are shiped with RT):
gtk2 files
delete them
dlls
The list in rawpedia is ok except the error in libbz2-1 name
Adwaita icons
icons/Adwaita/16x16/actions/*
icons/Adwaita/16x16/devices/*
icons/Adwaita/16x16/mimetypes/*
icons/Adwaita/16x16/places/*
icons/Adwaita/16x16/status/*
icons/Adwaita/48x48/devices/*
icons/Adwaita/24x24/status/image-missing.png
from prefix/share -> .share
Adwaita cursors
plus.cur
sb_h_double_arrow.cur
sb_left_arrow.cur
sb_right_arrow.cur
sb_v_double_arrow.cur
from prefix/share/icons/Adwaita/cursors
-> ./share/icons/Adwaita.cursors
adwaita files
icon-theme.cache
index.theme
from prefix/share/icons/Adwaita
-> ./share/icons/Adwaita
Schemas
prefix/share/glib-2.0/schemasgschemas.compiled -> ./share/glib-2.0/schemas
gdk pixbuf
prefix/lib/gdk-pixbuf-2.0/* -> ./lib/gdk-pixbuf-2.0
@sguyader can you modify rawpedia?
For those interested, This is the simplest way I found to create subdirectories and copy the files
# Icons
listedirs=" icons/Adwaita/16x16/actions
icons/Adwaita/16x16/devices icons/Adwaita/16x16/mimetypes
icons/Adwaita/16x16/places icons/Adwaita/16x16/status
icons/Adwaita/48x48/devices "
for v in $listedirs
do
robocopy $prefix/share/$v $destination/share/$v -s 1>/dev/null
done
robocopy $prefix/share/icons/adwaita/24x24/status $destination/share/icons/adwaita/24x24/status image-missing.png 1>/dev/null
#cursors
robocopy $prefix/share/icons/Adwaita/cursors $destination/share/icons/Adwaita/cursors plus.cur \
sb_h_double_arrow.cur sb_left_arrow.cur sb_right_arrow.cur sb_v_double_arrow.cur 1>/dev/null
#schemas
robocopy $prefix/share/glib-2.0/schemas $destination/share/glib-2.0/schemas gschemas.compiled 1>/dev/null
#Adwaita files
robocopy $prefix/share/icons/Adwaita $destination/share/icons/Adwaita \
icon-theme.cache index.theme 1>/dev/null
#gdk-pixbuf
robocopy $prefix/lib/gdk-pixbuf-2.0 $destination/lib/gdk-pixbuf-2.0 -s 1>/dev/null
I don’t know how to include the cursors into the repository of RawTherapee.
@TooWaBoo Thank you for the corrections. your changes are ok
Reading the windows page, I still have some corrections to propose:
- in second § replace
RawTherapee can be built using GTK+ versions 2 or 3. To build using GTK2 use the gtk2 branch; to build using GTK3 use the dev branch
by
Rawtherapee is built using GTK+ version 3.
-
suppress the paragraph “Download and build Clearlooks” as it will no longer be used
-
at the end of “Clone and build RawTherapee”, delete all text from
if you are building for 32-bit Windows XP until end of §
- in “Creating a distributable package” suppress:
The current WindowsInnoSetup.iss script is designed for the gtk2 branch until so that icons and schemas will be copied into the package.
- in same § delete
The gdb.exe binary, available from http://www.gnu.org/software/gdb/, should be copied into the RawTherapee installation folder and, if using Inno Setup to generate the package, the WindowsInnoSetup.iss script should be edited by uncommenting (removing the semicolon from the front of) the following around line 114 of the script:
;Source: “{#MyBuildBasePath}\gdb.exe”; DestDir: “{app}”; Flags: ignoreversion
-
replace
RawTherapee_<WinXP|WinVista><32|64>_.zip
"WinXP" means that the build is only for Windows XP. "WinVista" means it can run on any version of Windows from Vista upwards, including 10. The "version" will either look like 5.2 if you checkout the 5.2 tag, or 5.2-dev-g1a2b3c4d if you checkout the dev branch after 5.2 was tagged. If you are shipping more than one build type in an installer, include the names of all build types, e.g. release_debug.For example:
RawTherapee_WinVista_64_5.2_release.zip RawTherapee_WinVista_64_5.2_release_debug.zip RawTherapee_WinVista_64_5.2-dev-g1a2b3c4d_release_debug.zip
by
RawTherapee_<version>_<WinVista>_<64>.zip
. "WinVista" means it can run on any version of Windows from Vista upwards, including 10.
The "version" will either look like 5.2 if you checkout the 5.2 tag, or 5.2-xxx-g1a2b3c4d if you checkout the dev branch after 5.2 was tagged.
For example:
RawTherapee_5.2_WinVista_64.zip
RawTherapee_5.2-128-g1a2b3c4d_WinVista_64.zip
The gtk2, gtk3 and master branches are deleted. To build the GTK2 version checkout the 5.0-r1-gtk2 tag.
It’s fine to mention GTK2 but the guide should focus on building the dev branch using GTK3 and not confuse the user with info about building obsolete and unsupported versions.
And please try to avoid duplicating info since that makes maintenance more difficult. For example when describing branches you could just refer to Linux#Choose_a_branch, same for CMake options and any other information which does not significantly change between OSes.
Hello!
I’ve been using O/S specific dev builds from @gaaned92. I go to Google drive for these. It appears that the latest files available are dated in Oct 2023. I’m not sure if new releases will be available anytime soon.
I’ve also been using this script for darktable.
#!/bin/bash
lensfun-update-data
cd ~/darktable/
rm -rf build
git pull origin master
git submodule update
mkdir build
cd build
cmake -G Ninja -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/opt/darktable -DCUSTOM_CFLAGS=ON -DCMAKE_CXX_FLAGS=“-O3 -march=native” -DCMAKE_C_FLAGS=“-O3 -march=native” -DBINARY_PACKAGE_BUILD=OFF …/.
cmake --build . --target package
Can RawTherapee be compiled similarly?
You can try following the process of the nightly build: RawTherapee/.github/workflows/windows.yml at dev · Beep6581/RawTherapee · GitHub