| |
Burglar
Registered: Dec 2004
Posts: 1031 |
Cross Development using Makefile
Weekend didn't even start for most of you yet, but here it is ;)
Cross Development using Makefile
comments and improvements are of course very welcome.
enjoy and may your build times be short!
make -j16 |
|
... 37 posts hidden. Click here to view all posts....
|
| |
Danzig
Registered: Jun 2002
Posts: 428 |
Quote:Just to say it once: Forget the advice about cygwin. These days please use msys2 - which is nicer in every aspect.
anyone tried that jizzle with WSL2 with, say, debian? should even work with starting WinVice on the desktop!? |
| |
Stone
Registered: Oct 2006
Posts: 168 |
Quote: Just to say it once: Forget the advice about cygwin. These days please use msys2 - which is nicer in every aspect.
Indeed. And stay away from the packages you can find with chocolatey. Both 'make' and 'grep' are compiled without support for wildcards/glob patterns... |
| |
Frantic
Registered: Mar 2003
Posts: 1627 |
Quote: Indeed. And stay away from the packages you can find with chocolatey. Both 'make' and 'grep' are compiled without support for wildcards/glob patterns...
I would never ever install something called "chocolatey", no matter what it was. |
| |
Bacchus
Registered: Jan 2002
Posts: 154 |
@krill - of course. I am exploring moving away from bat files.
@groepaz - This is under Windows 11 and my shell has support for MAKE via the Embarcadero installation of Delphi I have. So MAKE work without any additional installation for me (I do have MSYS2 for building VICE as I presume you already know ;-)
The particular issue I had with segments in KickAssembler was solved. In the makefile define the address of where the patch is (so I can reuse that address for the calling address of the cruncher) and then the general build of the "import binary, patch and save a patched copy" is like this:
*=$0801
.segmentout [allowOverlap=true, segments="themain,themainpatch"]
.segment themain []
* = $0801
.import c64 "depacked/x.prg"
.segment themainpatch []
*=cmdLineVars.get("InsertCode").asNumber(16) |
| |
hollowman
Registered: Dec 2001
Posts: 474 |
Quote: Quote:Just to say it once: Forget the advice about cygwin. These days please use msys2 - which is nicer in every aspect.
anyone tried that jizzle with WSL2 with, say, debian? should even work with starting WinVice on the desktop!?
Yes, running Vice on the Windows desktop using WSL2 works fine for me so far. I use Windows 11 with WSL2 and Ubuntu 20 as Linux distribution.
And for development you can use Visual Studio Code with the remote WSL extension, so you have the VS Code UI running on the Windows desktop and the VS Code Server and your command line tools running under Linux in WSL2. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11100 |
Doesnt VS Code run in WSL2? |
| |
Danzig
Registered: Jun 2002
Posts: 428 |
Quote: Doesnt VS Code run in WSL2?
No, worse, Electron app alias Browser :-D |
| |
chatGPZ
Registered: Dec 2001
Posts: 11100 |
*gets the garlic out* |
| |
hollowman
Registered: Dec 2001
Posts: 474 |
Quote: Doesnt VS Code run in WSL2?
When running VS Code in WSL2 the VS Code server is running in WSL2, while the UI on the Windows desktop is the regular VS Code for Windows application acting as a client.
When running Vice in WSL2 the UI on the Windows desktop is an RDP session into the WSLg X/Wayland/Pulse Audio server.
 |
| |
Silver Dream !
Registered: Nov 2005
Posts: 107 |
Quote: When running VS Code in WSL2 the VS Code server is running in WSL2, while the UI on the Windows desktop is the regular VS Code for Windows application acting as a client.
When running Vice in WSL2 the UI on the Windows desktop is an RDP session into the WSLg X/Wayland/Pulse Audio server.
Is there any special reason for doing this kind of things instead of simply running GNU/Linux? Even in a VM if for some Very Important Reasons somebody cannot live w/o Windows on their machines? |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 - Next |
