Thanks Ian! |
I'm planning to use Mingw because it's already set up with Visual Studio Code.
Now I have 2 compilers on 2 different paths:
2. C:\msys64\mingw64\bin -- without this one I could't configure/make/make install FLTK from the mingw shell
If you say I should use Msys shell.... which doesn't find any compiler ("no acceptable C compiler found in $PATH")
probably I have to figure out how to make Msys shell to see the first compiler...
Indeed I'm new to this and very thankful for any hint in which direction to go next :)
On Saturday, September 19, 2020 at 7:16:12 PM UTC+2 Ian MacArthur wrote:
On Sat, 19 Sep 2020, 17:17 Theodore, wrote:
I followed the steps from the README.Windows file and I succeded installing FLTK from an Msys2 shell with the commands:
The problem is I don't know there where they are installed.
I was in the path C:\Program Files\fltk-1.4.x
So I assumed I installed them on this path.
=== quote ===
Then Msys will "install" the libraries to where it thinks the path "/usr/local/" leads to. If you only ever build code from within the Msys environment this works well, but the actual "Windows path" these files are located in will be something like "C:\msys\1.0\local\lib", depending on where your Msys installation is rooted, which may not be useful to other tools.
If you want to install your built FLTK libraries in a non-standard location you may do:
sh configure --prefix=C:/FLTK
=== end quote ===
So I created a new subfolder: "C:\Program Files\fltk-1.4.x\build" , I moved the "configure" file here and I tried to configure, build and install here.
But I get this error:
$ sh configure --prefix=C:/Program Files/fltk-1.4.x/build
sh: configure: No such file or directory
What am I doing wrong?
Thanks for taking the time to answer!
OK, first off, if you are planning on using the mingw tools as your build toolchain, then building from the Msys shell is by far the best option anyway.
So just do that, and it'll be fine!
If you need to see the path to where the files actually are, then typing "mount" in the Msys shell will show where the paths map to in the DOS environment, and you can figure it out from there.
Typically, it's all under the folder you install mingw to, so something like C:/mingw/lib or some such thing.
If you *don't* plan on using the mingw tool chain, then you should probably just get the free "community edition" of Visual Studio and use that.
Note that you can't really mix and match tool chains; you need to use one or other, but the libraries are not mutually compatible.
As to what went wrong when you moved the configure file.... Well, let's just say there are several things wrong with that approach and leave it at that.
I'm guessing you're new to this, but in a few weeks you'll know where you went awry...
From my Fairphone FP3
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/5505a9e0-baf4-4de6-b70f-d35f94a58767n%40googlegroups.com.
[ Direct Link to Message ]