|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows |
Date: | Mon, 28 Sep 2020 12:47:22 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.121 Safari/537.36 Edg/85.0.564.63 |
Follow-up Comment #10, bug #59173 (project octave): I was calling "mkoctfile" from the Octave prompt in comment #0. What John D was pointing out in comment #7 is probably related to these lines of code: https://hg.savannah.gnu.org/hgweb/octave/file/d28016d16e9a/src/mkoctfile.in.cc#l235 #if (defined (OCTAVE_USE_WINDOWS_API) || defined (CROSS)) || (defined __APPLE__ && defined __MACH__) // We'll be linking the files we compile with -loctinterp and -loctave, // so we need to know where to find them. DEFAULT_LDFLAGS += "-L" + quote_path (vars["OCTLIBDIR"]); #endif So no matter what `vars["LDFLAGS"]` is, there is a -L flag with the path to the Octave libraries when mkoctfile is called to compile .oct files. If a package wants to know which flags to use for linking to the Octave libraries, "mkoctfile -p" returns some flags that are nonsense (or incomplete) on Windows (and probably for any cross-builds) at the moment. For completeness, `LDFLAGS` isn't set in Octave on Windows: >> getenv('LDFLAGS') ans = >> The cross-build with this patch is almost finished. I'll report the results. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?59173> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |