Building FlightGear - Cross Compiling: Difference between revisions

Building FlightGear - Cross Compiling (view source)

73 bytes added , 27 May 2015

m

272

edits

@@ Line 126: / Line 126: @@
 </pre>
-the result will be a blank file, $(PREFIX)/i686-w64-mingw32.shared/installed/fgfs. in this case $(3) was replaced by the ${triplet}.${linker_configuration}. see: https://sourceforge.net/p/mingw-w64/wiki2/TypeTriplets/
+an installed/$(1) file, is a file indicating what MXE thought was a successful build, so a $(PREFIX)/$(3)/installed/fgfs, is an empty file generated for this purpose.
+$(PREFIX): returns the absolute path of ${mxe_dir}/usr
+$(3): is the triplet name, in the form of ${triplet}.${linker_configuration}. see: https://sourceforge.net/p/mingw-w64/wiki2/TypeTriplets/
-to obtain a cross-compilation of a useful software, MXE refers to a file that contains the string returned by software name, suffixed by .mk(example, fgfs.mk), in the mxe/src/ directory, you must provide this file to allow Makefile generation for software. otherwise, a minimal *.mk file will always return a successful build.
+to obtain a cross-compilation of a useful software, MXE refers to a file in the ${mxe_dir}/src/ directory that contains a file with string $(1), suffixed by ".mk" (example, fgfs.mk), this file is used for configuration and Makefile generation of software.
 === *.MK file ===