Not sure whether this forum is the right one, but from my understanding, installing MinGW-W64 from macports into macOS allows for cross-compiling Windows applications under macOS. I installed sudo port install x86_64-w64-mingw32-gcc So far so good. It worked flawlessly. But where does it install? What is the path to invoke the compiler binary or link libraries? I can hardly find any documentation for this. First thing was to run sudo /usr/libexec/locate.updatedb to find out it is in /opt/local/x86_64-w64-mingw32...
Actually I was expecting that I'd get a hex number with lower case hex digits when specifying the following format: (format out "_pnames=0x~x;~." *pnames* ) _pnames=0x80B9; But actually I'm getting upper-case 'B' instead of 'b'. Am I overlooking something?
Actually I was expecting that I'd get a hex number with lower case hex digits when specifying the following format: (format out "_pnames=0x~x;~." *pnames* ) _pnames=0x80B9; But actually I'm getting upper-case 'B' instead of 'b'. Am I overlooking something?
Actually I was expecting that I'd get a hex number with lower case hex digits when specifying the following format: (format out "_pnames=0x~x;~." *pnames* ) _pnames=0x80B9; But actually I'm getting upper-case 'B' instead of 'b'. Am I overlooking something?
OK. Thanks for pointing my nose on it :). At least we found the solution. Will do the icon substitution now and let you know of the outcome. EDIT: it worked. Was tedious to create all these icons but finally it worked out.
OK. Thanks for pointing my nose on it :). At least we found the solution. Will do the icon substitution now and let you know of the outcome.
Please discard my desription about using mklink /h. I state the icon mechanism still doesn't work under 6.73. I did a make of my project once with c:\freewrap by swapping the contents between freewrap.673 and freewrap.664. When looking directly in explorer details view at the myexe.exe I see the icon in the 664 case, and the tcl/tcsh default icon with the exe in the 673 case. No links involved. C:\Projekte\myexe>file myexe.ico myexe.ico: MS Windows icon resource - 3 icons, 32x32, 8 bits/pixel, 32x32,...
Please discard my desription about using mklink /h. I state the icon mechanism still doesn't work under 6.73. I did a make of my project once with c:\freewrap by swapping the contents between freewrap.673 and freewrap.664. When looking directly in explorer details view at the myexe.exe I see the icon in the 664 case, and the tcl/tcsh default icon with the exe in the 673 case. No links involved. C:\Projekte\myexe>file myexe.ico myexe.ico: MS Windows icon resource - 3 icons, 32x32, 8 bits/pixel, 32x32,...
Please discard my desription about using mklink /h. I state the icon mechanism still doesn't work under 6.73. I did a make of my project once with c:\freewrap by swapping the contents between freewrap.673 and freewrap.664. When looking directly in explorer details view at the myexe.exe I see the icon in the 664 case, and the tcl/tcsh default icon with the exe in the 673 case. No links involved. C:\Projekte\myexe>file myexe.ico myexe.ico: MS Windows icon resource - 3 icons, 32x32, 8 bits/pixel, 32x32,...
Please discard my desription about using mklink /h. I state the icon mechanism still doesn't work under 6.73. I did a make of my project once with c:\freewrap by swapping the contents between freewrap.673 and freewrap.664. When looking directly in explorer details view at the myexe.exe I see the icon in the 664 case, and the tcl/tcsh default icon with the exe in the 673 case. No links involved. C:\Projekte\myexe>file myexe.ico myexe.ico: MS Windows icon resource - 3 icons, 32x32, 8 bits/pixel, 32x32,...
Please discard my desription about using mklink /h. I state the icon mechanism still doesn't work under 6.73. I did a make of my project once with c:\freewrap with freewrap.673 in the contents. When looking at the myexe.exe I see the icon in the 664 case, and the tcl/tcsh default icon with the exe in the 673 case. No links involved. C:\Projekte\myexe>file myexe.ico myexe.ico: MS Windows icon resource - 3 icons, 32x32, 8 bits/pixel, 32x32, 16 colors, 4 bits/pixel I'm sitting in the physical directory...
The problem is still there in 6.73 (Windows 10 Pro). When I create a (symbilic) link (MKLINK /H ) on the desktop, the program icon is not shown, instead the tcl/tcsh defaut icon Going back to 6.64 shows the icon.
What would I best refer to when it comes to a full comprehensive language reference? Can I still use Steeles Book "Common Lisp"?
I thought that too, in the first place, but it gives (Windows 8.1) : module ’syscalls’ requires package POSIX On the Windows 10 system the latest clisp gives: C:\Projekte\forth>\clisp\clisp --version GNU CLISP 2.49 (2010-07-07) (built on STSst063.jenty.by [150.0.0.63]) Software: GNU-C 3.4.5 (mingw-vista special r3) gcc -mno-cygwin -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensive-optimizations -falign-functions=4...
Found that I had to invoke C:\clisp\full\lisp.exe instead.
I installed the most recent version (2.49) under Windows 8.1 and got an error when invoking clisp with the following command line: C:\Projekte>c:\clisp\clisp.exe -B "C:/clisp/" -M "C:\clisp\/full/lispinit.mem" "myapp.lisp" 1>myapp.txt C:/clisp//base/lisp.exe: initialization file `C:\clisp\/full/lispinit.mem' was not created by this version of CLISP runtime
I installed the most recent version (2.49) under WIndows 8.1 and got an error when invoking clisp with the following command line: C:\Projekte>c:\clisp\clisp.exe -B "C:/clisp/" -M "C:\clisp\/full/lispinit.mem" "myapp.lisp" 1>myapp.txt C:/clisp//base/lisp.exe: initialization file `C:\clisp\/full/lispinit.mem' was not created by this version of CLISP runtime
Hi, I'm new to Clisp. How can I find out the version of Clisp that is installed?
I see this being an issue posted here already. I stepped back to 6.70, still the issue. It works in 6.64. After going back to 664 and then up to 672 again, the .exe has the ico-file attached. Strange. EDIT: false alarm, the icon when attached to the task bar, still has the tcl/tk icon. How do I find out the freewrap version?
I see this being an issue posted here already. I stepped back to 6.70, still the issue. It works in 6.64. After going back to 664 and then up to 672 again, the .exe has the ico-file attached. Strange. How do I find out the freewrap version?
I see this being an issue posted here already. I stepped back to 6.70, still the issue. It works in 6.64.
I have the following line in my make.bat: ..\freewrap\win64\freewrap.exe hismain.tcl -f files.txt -i hismain.ico -o .\hismain_dist\win64\hismain.exe The funny thing is that the icon is not attached. Instead the .exe has the tcl/tk icon. I'm speaking of the explorer view of the .exe.
Thanks. This helped. All references to scripts and other files for the project were wired relative to the project, e.g. /hismain/source/utils.tcl. Changing all these occurences to /zvfs/Projekte/hismain... cured the problem. Could there be a special "Prefix"-variable for this situation in 6.7?
I adopted a project from someone. I don’t know whether the problem I have is related to the version of freewrap. Anyway, the following happens: His make.bat contains the following commands: ..\freewrap\win32\freewrap.exe hismain.tcl -f files.txt -i hismain.ico -o .\hismain_dist\win32\hismain.exe -w ../freewrap/win32/freewrap.exe ..\freewrap\win64\freewrap.exe hismain.tcl -f files.txt -i hismain.ico -o .\hismain_dist\win64\hismain.exe copy .\hismain.ini .\hismain_dist\win32\hismain.ini copy .\hismain.ini...
I adopted a project from someone. I don’t know whether the problem I have is related to the version of freewrap. Anyway, the following happens: His make.bat contains the following commands: ..\freewrap\win32\freewrap.exe hismain.tcl -f files.txt -i hismain.ico -o .\hismain_dist\win32\hismain.exe -w ../freewrap/win32/freewrap.exe ..\freewrap\win64\freewrap.exe hismain.tcl -f files.txt -i hismain.ico -o .\hismain_dist\win64\hismain.exe copy .\hismain.ini .\hismain_dist\win32\hismain.ini copy .\hismain.ini...
I adopted a project from someone. I don’t know whether the problem I have is related to the version of freewrap. Anyway, the following happens: His make.bat contains the following commands: .\freewrap\win32\freewrap.exe hismain.tcl -f files.txt -i hismain.ico -o .\hismain_dist\win32\hismain.exe -w ../freewrap/win32/freewrap.exe ..\freewrap\win64\freewrap.exe hismain.tcl -f files.txt -i hismain.ico -o .\hismain_dist\win64\hismain.exe copy .\hismain.ini .\hismain_dist\win32\hismain.ini copy .\hismain.ini...
I adopted a project from someone. I don’t know whether the problem I have is related to the version of freewrap. Anyway, the following happens: His make.bat contains the following commands: .\freewrap\win32\freewrap.exe hismain.tcl -f files.txt -i hismain.ico -o .\hismain_dist\win32\hismain.exe -w ../freewrap/win32/freewrap.exe ..\freewrap\win64\freewrap.exe hismain.tcl -f files.txt -i hismain.ico -o .\hismain_dist\win64\hismain.exe copy .\hismain.ini .\hismain_dist\win32\hismain.ini copy .\hismain.ini...
I adopted a project from someone. I don’t know whether the problem I have is related to the version of freewrap. Anyway, the following happens: His make.bat contains the following commands: .~~~ .\freewrap\win32\freewrap.exe hismain.tcl -f files.txt -i hismain.ico -o .\hismain_dist\win32\hismain.exe -w ../freewrap/win32/freewrap.exe ..\freewrap\win64\freewrap.exe hismain.tcl -f files.txt -i hismain.ico -o .\hismain_dist\win64\hismain.exe copy .\hismain.ini .\hismain_dist\win32\hismain.ini copy .\hismain.ini...
I adopted a project from someone. I don’t know whether the problem I have is related to the version of freewrap. Anyway, the following happens: His make.bat contains the following commands: ..\freewrap\win32\freewrap.exe hismain.tcl -f files.txt -i hismain.ico -o .\hismain_dist\win32\hismain.exe -w ../freewrap/win32/freewrap.exe ..\freewrap\win64\freewrap.exe hismain.tcl -f files.txt -i hismain.ico -o .\hismain_dist\win64\hismain.exe copy .\hismain.ini .\hismain_dist\win32\hismain.ini copy .\hismain.ini...