1) Sbcl binaries via SourceForge are OK.
2) You can build it yourself from source if you want. It's not that hard. Install msys2, then install gcc via pacman, the package manager. Then build sbcl as described in docs, voila.
I use both the MSVC
and gcc
via MSYS2
(MSYS*<em>2</em>* is not the same as the old MSYS). As for the VSCode experience for C(++)... I found it to be pretty good in conjunction with CMake and CMake extension. Remember that technically, VSCode is not an IDE, so it doesn't have any kind of project control for C(++) or any other language. That's why I use CMake. It comes with portability as a bonus, instead of nasty, non-portable, VS project files. If you can you can explore my .vscode settings for anything you might find useful.
Msys 2 (http://www.msys2.org/) is a port of many Linux tools directly to Windows. It ports Arch Linux's package manager, and, in its repositores it contains many libraries and many development tools (ie. make, cmake, g++, probably clang). It also supports compiling exes that can be run on Windows without Msys. It is based on cygwin and mingw, but is a separate project from each of these and ensures that all of your C++ tools are as well integrated as they are in an actual Linux environment.
Although, really, the best way to develop C++ is to just do it on Linux and only worry about Windows come distribution time. This is practical if you use only libraries that work on both systems (ie. SFML, OpenGl, Vulkan, GTK, Qt, Boost). Conan can also help with this, although, IMO, Linux and its amazing library system to develop with and msys 2 to port to Window is superior to conan, mainly due to the vastly larger number of libraries available.
You can install msys2 http://www.msys2.org/
Download the package and install it (sometimes it calls for suspicious net activity for some antivirus, so you might be aware of that).
It install a minimal cli environment.
For example install bash: pacman -S bash
If you need to search a specific package ie. gtk it will list all gtk packages: pacman -Ss gtk
Consult the wiki
https://github.com/msys2/msys2/wiki
Edit: Also all the downloads are stored in C:/msys64/var/cache/pacman/pkg
So you can copy them, and install them offline like this
cd <where the files are> pacman -U ./*
It can be on Windows natively as part of msys2, and it does checksums on a per-chunk basis, so it'll actually save you a lot of copying if files don't change much. You can wrap it to do any sort of checks you want with the --dry-run
option combined with --existing
/--ignore-existing
/--delete
.
> I used cygwin to install autoconf, automake, and libtools via this question, however when I went to the gambit directory to execute commands such as ./configure and aclocal they aren't recognized.
Actually a legit suggestion - use any Linux distribution instead of Windows. Using mingw to compile something designed for Linux-like system written in C is always a pain in the ass and I am pretty sure that your entire problem would disappear if you typed sudo apt install build-essential
on Ubuntu/Debian.
That being said - assuming that you are using a proper setup of MSYS2 (aka one from here: http://www.msys2.org/) then you need install those extra things via pacman (available once you use msys shell, probably mingw64.exe one for you) to make it work on Windows:
Once I got those 4 gambit seemed to generate all configuration files correctly and from there it's just ./configure
, make -j CXXGLAGS+=fpermissive
and make install -j CXXFLAGS+=-fpermissive
(you might need to do pacman -S mingw-w64-x86_64-toolchain first to get a working mingw compiler).
Warning - this thing is surprisingly time consuming to compile from what I just checked. On an 8 core CPU (if you use make -j so it multithreads) it takes roughly 30 seconds to compile once you do make and make install.
I use msys2 which comes with windows version of the linux tools (doesn't include everything though).
By works with windows I mean the dependencies (generated .dep file) part works with windows paths, because the website I got the original makefile from had it only working for linux paths.
I do occasionally use visual c++ express for debugging if I'm too lazy to use gdb, but I mainly use emacs + gcc.
i am using MSYS2 because it already offers:
pacman -S base-devel
after installation, launch and update),pacman
as a package manager, ported over from Arch Linux to Windows,This guide may be of interest to you if you want to stay with the more common CygWin instead of MSYS2.
Sure I would love to use Linux. But my workplace didn't treat me like a special snowflake. Over the years I've accustomed so much to curing Windows from its lack of useful software that I became too lazy to change my workstation at home.
In my experience some libraries are even easier to get for the GNU version. I'm using it without problems on Windows.
You can also set up MSYS2 to easily install C libraries to use with Rust: http://www.msys2.org/ I'll try to write a guide in the next days on how to do that :)
I've been using Go in a Windows environment for a while. Here's my three steps setup.
Copying to the top-level comment:
I tried to compile your code with first MinGW i found in Google and got results similar to yours: window popping up and closing.
On closer inspection it seems like compiler i used was not compatible with libtcod version used in tutorial. Tutorial states that you NEED to use 32-bit g++, but i never managed to force 32-bit MinGW install.
On the other hand, when using 32-bit http://www.msys2.org/ installer (msys2-i686-20180531.exe
at the time of this comment) with the same libtcod i have that same code compiling and running OK.
So, please, can you state what versions of MinGW and libtcod are you using?
I switched to another version of MinGW32 (32-bit from http://www.msys2.org/) and i could compile OPs code with libtcod 1.5.1. So maybe checking/changing compiler setup can help OP too?
Offtopic saltiness: it's kinda aggravating how many options of C/C++ instruments are available for Windows (close to infinity... or maybe even more nowadays) compared to how many of them are tested/documented (close to zero... or maybe even less). Setting things up on Windows is constant hassle. I.E. when i tried to install Rust compiler some time ago, docs stated that i need to install VS Build tools and select "Windows 10 SDK" when doing so. OK. I download installer, run it... and i see goddamn 6 (SIX!) different things labeled "Windows 10 SDK". Some hacking with new languages can be fun, but when you need to start hacking even before installing the compiler - it beyond evil.
Can't help you with visual studio I'm afraid, but if I may offer an alternative. Fuck visual studio and use nice free software tools like GCC and a nice UNIX shell. You can install all this extremely easily with the msys2 installer. Further bonus: it comes with a package manager that you can use to install text editors like vim, build tools like GNU make and cmake, and any library you care to use like freeglut and SDL2, with a simple command and no further fuss. Here's the link: http://www.msys2.org/
Rsync is a god send when dealing with transfers of large files over a network. I don't think there are any Windows tools that does the same.
I run a lot of Linux tools on Windows like git and ssh.
For running Linux tools you have basically three alternatives.
I got rsync to work with msys2 as a native executable in powershell. Then you don't have to invoke cygwin and bash to run rsync. You should check it out.
Ok, are you on Windows? I don't use Windows for programming, but from what I am reading it looks like you need to install MSYS2 Then open the MSYS2 shortcut, it should be in Start menu or desktop maybe.... that will give you a command prompt... then cd into the folder where you installed QMK, qmk_firmware folder, and run the script.... util/msys2_install.sh that will install your build environment. Then you can make your hex file.
The current approach taken by Emacs Powerpack is not to include additional helper programs but instead to suggest that you use the msys2 installer here http://www.msys2.org/ and msys2 package manager to install additional unix-like programs. The default configuration which Emacs Powerpack installs will by default use the msys2 shell if it can find it as the base shell for things like M-x shell, M-x grep (of course this can be changed).
You should be able to do everything in the tutorial with either the Windows Subsystem for Linux or Cygwin (I recommend Msys2 if you go this route which is sort of a distro for Cygwin). You should be able to install Qemu for Windows too though (although I have no idea how well if at all it works).
So I followed the directions found on http://www.msys2.org/ I had to use pacman -Syu and pacman -Su if that helps. I tried to follow the instructions afterwards found on qmk website
I'm stuck here now. I'm a newbie at this kinda stuff and I thought I should try to set this up before building my planck tomorrow! Thanks
Even Microsoft says to use vcpkg instead of nuget - https://github.com/Microsoft/vcpkg/blob/master/docs/about/faq.md#why-not-nuget
Also vcpkg covers only MSVC compiler, for GCC I recommend Msys2 - http://www.msys2.org/
Install MSYS2: http://www.msys2.org/
Find a package name: pacman -Ss foo (or look through here to see everything available.)
Install it: pacman -S mingw-w64-foo (or whatever)
????
Profit!