@damarko
This issue was solved by a modification made after 5.3. So the new builds should start much faster.
You can get development builds and feature builds here:
Without these icons, I see some missing icons (for example “Home” icon) in Preferences > File Browser > opening the dialog for “Other” for “Image Directory at Startup”.
I don’t have (and don’t seem to need):
the Adwaita cursors
./lib/gdk-pixbuf-2.0 (in fact I don’t have the .lib directory at all, wasn’t it needed only for Gtk2 builds?)
I also made my own lensfun build, so I can’t comment on this.
My expertise in Windows builds has decreased a lot since @gaaned92 started to make them much quicker than I was able to do (my own OS is Linux, so I haven’t made any Windows build since 5.3-rc1 I think).
Thanks.
The main difference in your build flags is the use of march=native instead of mtune=generic I use to be able to distribute the builds.
Effectively you build seems to start faster. On my machine (i6700K) its not really noticeable as your build takes about 2s to start on empty dir.
I will try the other flags I don’t use to see if it improves the speed.
@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.
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…
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
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
