Normally, the approach is either if the native tools are distributed, use them for build. There it might be needed to detect on configure time when cross-compiling. If they are internal and not distributed, there is a possibility to build the native build and then build in other directory a cross-build. Some packages use this system and give the configure option for directory with native build. Cheers F. On 24/10/17 09:38, Roger Oberholtzer wrote:
I am trying to build a Tcl/Tk extension in OBS. It is called TkImg. It adds support for more image formats. The issue I have is that it insists on building with support for libtiff. And that build wants to run a program that is has just built to generate code for the next part of the build. Unfortunately, the program is a .exe, and so this fails.
chmod u+x mkg3states.exe ./mkg3states.exe -b -c const tif_fax3sm.c ./mkg3states.exe: ./mkg3states.exe: cannot execute binary file Makefile:356: recipe for target 'tif_fax3sm.c' failed make[1]: *** [tif_fax3sm.c] Error 126 make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/tkimg/libtiff'
I don't really need tiff support, so I could patch this build so it does not include tiff support. But I wonder if there isn't a different approach I might take where I patch the build so that it uses wine to run the .exe to generate the code?
Has anyone done this in OBS? Any reason it would not work?
-- Please avoid sending me Word, Excel or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html