Open Losses opened 4 weeks ago
Well Amber hasn't been tested on Windows, so I'm actually surprised you got the binary to compile at all.
src/amber/cli.cr
try compiling that one and see if things run.@crimson-knight
Thank you for the quick response.
Actually, the compilation process has indeed been challenging, with a significant issue arising during dependency installation due to the absence of sqlite3.lib. To resolve this, a manual compilation of sqlite3.lib was necessary, followed by placement in the lib
folder within the Crystal executable directory.
During the compilation of cli.cr
, the following error was encountered:
In lib\teeplate\src\lib\file_tree.cr:8:10
8 | {{ run(__DIR__ + "/file_tree/macros/directory", dir.id) }}
^--
Error: error executing macro 'run':
Could you please provide any additional suggestions or insights that might help resolve the macro execution error? Your expertise in this matter would be greatly appreciated.
with a significant issue arising during dependency installation due to the absence of sqlite3.lib
Related: https://github.com/amberframework/micrate/issues/87
@Losses the last message there has me stumped. Macro's a notoriously obscure with the error message. I think you've hit the same point where most people switch to WSL2 or Docker to run Amber on Windows.
You will need to replace the forward slashes with back slashes on Windows.
@drujensen Hi! Thank you for the quick response, I have tried your solution but it seems not working
Description: I am experiencing issues when trying to use the Amber Framework on the Windows platform. Although Crystal can now be compiled on Windows, Amber Framework still faces some challenges. The official build instructions require users to use
make
for compilation, butmake
is not natively available on Windows.When attempting to compile using the
crystal build src/amber.cr
command directly, the resulting executable does not produce any output. This makes it difficult to use Amber on Windows and hampers development efforts.Steps to Reproduce:
crystal build src/amber.cr
.Expected Behavior: The executable should run and produce the expected output, similar to how it functions on Unix-based systems.
Actual Behavior: The executable runs but does not produce any output.
Suggested Improvements:
make
, or provide a Windows-compatible equivalent.Thank you for your attention to this matter. Your assistance in improving Windows support for the Amber Framework would be greatly appreciated.