<feed xmlns='http://www.w3.org/2005/Atom'>
<title>lanes/.runsettings, branch master</title>
<subtitle>A mirror of https://github.com/LuaLanes/lanes.git
</subtitle>
<id>https://git.lua4.win/lanes/atom?h=master</id>
<link rel='self' href='https://git.lua4.win/lanes/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lanes/'/>
<updated>2025-04-04T16:28:16+00:00</updated>
<entry>
<title>UnitTest vcproj builds exe directly in _LuaVersions so that it finds the necessary DLLs</title>
<updated>2025-04-04T16:28:16+00:00</updated>
<author>
<name>Benoit Germain</name>
<email>benoit.germain@ubisoft.com</email>
</author>
<published>2025-04-04T16:28:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lanes/commit/?id=5e29202b78d4932db079b21f0324ea57d8902bda'/>
<id>urn:sha1:5e29202b78d4932db079b21f0324ea57d8902bda</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fix Catch2 runsettings (getting there)</title>
<updated>2025-03-21T17:21:51+00:00</updated>
<author>
<name>Benoit Germain</name>
<email>benoit.germain@ubisoft.com</email>
</author>
<published>2025-03-21T17:21:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lanes/commit/?id=e627463246b7b1dffcc532a1f2ae2a6926ab4372'/>
<id>urn:sha1:e627463246b7b1dffcc532a1f2ae2a6926ab4372</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Adjusting MSVC files to ease unit testing</title>
<updated>2025-03-21T15:53:25+00:00</updated>
<author>
<name>Benoit Germain</name>
<email>benoit.germain@ubisoft.com</email>
</author>
<published>2025-03-21T15:53:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lanes/commit/?id=ab6f397df60c7ff6116705b7d045a990979176aa'/>
<id>urn:sha1:ab6f397df60c7ff6116705b7d045a990979176aa</id>
<content type='text'>
* Everything assumes there is a _LuaVersions folder containing all supported Lua versions (binaries, libs and headers) alongside the Lanes.sln location
* After that the solutions to build the Lua binaries themselves will appear too for reference (mainly because their output folders will be configured accordingly)
</content>
</entry>
</feed>
