272
edits
Hamzaalloush (talk | contribs) |
|||
Line 69: | Line 69: | ||
This isn't relevant at the moment, but referring to the Superbuild related comments above: it seems we could end up with a viable workaround by figuring out if/how and where those *.mk files are getting the value for <nowiki>-DCMAKE_TOOLCHAIN_FILE='$(CMAKE_TOOLCHAIN_FILE)'</nowiki> from - i.e. '''CMAKE_TOOLCHAIN_FILE''' specifically, and directly reuse that in the Superbuild (need to check if that'd work). But if it's too much of a hassle, let's just focus on *.mk files for starters. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 17:06, 28 May 2015 (EDT) | This isn't relevant at the moment, but referring to the Superbuild related comments above: it seems we could end up with a viable workaround by figuring out if/how and where those *.mk files are getting the value for <nowiki>-DCMAKE_TOOLCHAIN_FILE='$(CMAKE_TOOLCHAIN_FILE)'</nowiki> from - i.e. '''CMAKE_TOOLCHAIN_FILE''' specifically, and directly reuse that in the Superbuild (need to check if that'd work). But if it's too much of a hassle, let's just focus on *.mk files for starters. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 17:06, 28 May 2015 (EDT) | ||
: sure, it's stored in mxe/usr/${triplet-name}/share/cmake/mxe-conf.cmake, i'm sorry if this is not the place to include here, but here is it's contents anyway, autotools has similar implementation with $(MXE_CONFIGURE_OPTS), for autotools that is contained in the Makefile IIRC. mxe-conf.cmake: -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 17:14, 28 May 2015 (EDT) | :sure, it's stored in mxe/usr/${triplet-name}/share/cmake/mxe-conf.cmake, i'm sorry if this is not the place to include here, but here is it's contents anyway, autotools has similar implementation with $(MXE_CONFIGURE_OPTS), for autotools that is contained in the Makefile IIRC. mxe-conf.cmake: -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 17:14, 28 May 2015 (EDT) | ||
<syntaxhighlight lang="cmake"> | <syntaxhighlight lang="cmake"> | ||
Line 99: | Line 99: | ||
: thanks, you spared me quite a bit of searching here - I think this should already be a good way to play with getting the [[Superbuild]] to work at some point, without it necessarily having to invoke/involve mxe *.mk files. Basically, we would need the equivalent of some kind of '''mxe-config''' script that provides the corresponding path for such keys (e.g. the CMAKE_TOOLCHAIN_FILE) so that this can be reused elsewhere, without having to hard-code any paths.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 17:19, 28 May 2015 (EDT) | : thanks, you spared me quite a bit of searching here - I think this should already be a good way to play with getting the [[Superbuild]] to work at some point, without it necessarily having to invoke/involve mxe *.mk files. Basically, we would need the equivalent of some kind of '''mxe-config''' script that provides the corresponding path for such keys (e.g. the CMAKE_TOOLCHAIN_FILE) so that this can be reused elsewhere, without having to hard-code any paths.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 17:19, 28 May 2015 (EDT) | ||
:: hi, so all you need is an provoking script that initialize that file/set var as a standalone? And then it should be straightforward to adopt for the supper build? Then what happens to this project, is this just an exercise for cross-compiling FG? Or merely an extension to the Super build like d&c currently -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 11:39, 29 May 2015 (EDT) | |||
== .deb packaging == | == .deb packaging == |
edits