Errors encountered during Windows 10 build process

Development Building synfig
1

I have went through the cycle of building a minimum of three times and it still doesn’t work.(first time didn’t build, second time was built but IDE wasnt able to debug, third same as second) for various reasons each time so I thought maybe documenting the errors here would help so that I could get some insight onto what was happening.
The first error encountered was after running
./1-setup-windows-msys2.sh

at the end it said

1 out of 1 hunk FAILED
patching file /mingw64/include/libintl.h
Hunk #1 FAILED at 359.
1 out of 1 hunk FAILED – saving rejects to file /mingw64/include/libintl.h.rej

2

Then we may have to modify the patch tothis file:

3

Should I open an issue in Github?

4

Also when running
$ ./2-build-debug.sh

I got a multiple of the these:

*** Warning: This system cannot link to static lib archive C:/msys64/home/20102/synfig.git/_debug/build/lib/libsynfig.la.
*** I have the capability to make that library automatically link in when
*** you link to this library. But I can only do this if you have a
*** shared version of the library, which you do not appear to have.

*** Warning: linker path does not have real file for library -ldl.
*** I have the capability to make that library automatically link in when
*** you link to this library. But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because I did check the linker path looking for a file starting
*** with libdl and none of the candidates passed a file format test
*** using a file magic. Last file checked: C:/msys64/mingw64/lib/libdl.a
*** The inter-library dependencies that have been dropped here will be
*** automatically added whenever a program is linked with this library
*** or is declared to -dlopen it.

*** Since this library must not contain undefined symbols,
*** because either the platform does not support them or
*** it was explicitly requested with -no-undefined,
*** libtool will only create a static version of it.

5

Also noticed much of the errors aare with building synfig studio here is an example
CXXLD synfigstudio.exe
C:/msys64/mingw64/bin/…/lib/gcc/x86_64-w64-mingw32/11.2.0/…/…/…/…/x86_64-w64-mingw32/bin/ld.exe: error: export ordinal too large: 73254
collect2.exe: error: ld returned 1 exit status
make[4]: *** [Makefile:1640: synfigstudio.exe] Error 1
make[4]: Leaving directory ‘/home/20102/synfig.git/_debug/synfig-studio/src/gui’
make[3]: *** [Makefile:4088: all-recursive] Error 1
make[3]: Leaving directory ‘/home/20102/synfig.git/_debug/synfig-studio/src/gui’
make[2]: *** [Makefile:450: all-recursive] Error 1
make[2]: Leaving directory ‘/home/20102/synfig.git/_debug/synfig-studio/src’
make[1]: *** [Makefile:693: all-recursive] Error 1
make[1]: Leaving directory ‘/home/20102/synfig.git/_debug/synfig-studio’
make: *** [Makefile:529: all] Error 2

6

I noticed you’re the same user who was assigned this issue on GitHub
Since you’re going to hack only the UI you don’t really need the debug feature unless you want to go in-depth with Synfig backend parts like rendering, performance optimization, crashes, etc.

If Synfig is building and running I recommend prioritizing working on your assigned issue and worrying about the faulty build process afterward. I don’t have a Windows system with me so I don’t understand how and why Synfig build scripts are not working right on your system.

7

Yes, I actually was about to do that but the thing is. The best I reached was being able to run the app from the command prompt. However, even the source code itself when opened from the IDE give out errors for missing definitions and such. So I was thinking of working on it in a very manual way where I would edit the code then run from the command prompt to see what happens but I was having doubts about the effectiveness of that but ok thanks will do so then.