We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MSVC project files (.sln and friends) have been our burden. Because their format, structure and convention have been (will be) changed randomly.
To ease this problem, I made a simple batch script which invokes cl.exe (MSVC compiler/linker driver) and rc.exe directly.
cl.exe
rc.exe
It's cumbersome, but its core is the following one line:
cl.exe %COMPILER_OPTIONS% %SRCS% /link %LINKER_OPTIONS% lz4.res
It passes compiler options, source files, linker options and resource file.
The text was updated successfully, but these errors were encountered:
gist
Procedure:
cmd.exe cd /d "%USERPROFILE%\Documents" md lz4-issue-1386 cd lz4-issue-1386 git clone https://github.com/lz4/lz4.git cd lz4 md build\visual_studio\lz4 cd build\visual_studio\lz4 copy ..\..\VS2022\lz4\lz4.rc . curl -JOL https://gist.githubusercontent.com/t-mat/de819af37d3dd399147a75f9af1b034e/raw/build-vs2022.cmd type build-vs2022.cmd | find "" /V > build-vs2022.cmd.bat .\build-vs2022.cmd .\lz4.exe --version
Sorry, something went wrong.
Yes, this is a good idea.
No branches or pull requests
MSVC project files (.sln and friends) have been our burden. Because their format, structure and convention have been (will be) changed randomly.
To ease this problem, I made a simple batch script which invokes
cl.exe
(MSVC compiler/linker driver) andrc.exe
directly.It's cumbersome, but its core is the following one line:
It passes compiler options, source files, linker options and resource file.
The text was updated successfully, but these errors were encountered: