emileclarkb/hammer
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
hammer/tools/windows/hammer_lib_src_list

50 lines
805 B
Text
Raw Normal View History

windows build: Add build scripts + appveyor.yml In order to guarantee that Hammer can build on Windows, an appveyor.yml and associated build scripts will build hammer and its examples. The idea is that as soon as the appveyor.yml exists in the repository, pull requests that would impede Windows portability would be immediately detected. The scripts expect CL.EXE to be in the path, and will produce their results in build/ The highest level of warning is enabled on CL.EXE, minus warnings that bring CL.EXE to a level that ressembles C99. The only notable warning that was disabled is the one that tells you about implicit truncating conversions. Hammer's source code has quite a few implicit conversions say from a 64bit unsigned integer to a integer of a lesser size (signed or otherwise)
2015-08-09 15:20:43 +02:00
platform_win32.c
Implement h_platform_stopwatch for Windows We use QueryPerformanceCounter which will return realtime, not user time.
2015-08-15 13:47:34 +02:00
allocator.c
benchmark.c
windows build: Add build scripts + appveyor.yml In order to guarantee that Hammer can build on Windows, an appveyor.yml and associated build scripts will build hammer and its examples. The idea is that as soon as the appveyor.yml exists in the repository, pull requests that would impede Windows portability would be immediately detected. The scripts expect CL.EXE to be in the path, and will produce their results in build/ The highest level of warning is enabled on CL.EXE, minus warnings that bring CL.EXE to a level that ressembles C99. The only notable warning that was disabled is the one that tells you about implicit truncating conversions. Hammer's source code has quite a few implicit conversions say from a 64bit unsigned integer to a integer of a lesser size (signed or otherwise)
2015-08-09 15:20:43 +02:00
bitreader.c
bitwriter.c
Remove warning about tail "potentially uninitialized" MSVC was complaining that the `tail` variable was potentially uninitialized in the while branch. Since the while loop is actually coupled to the if (head != NULL) that initializes the tail variable, we move them together, which makes the warning disappear.
2016-01-31 16:55:17 +01:00
cfgrammar.c
datastructures.c
windows build: Add build scripts + appveyor.yml In order to guarantee that Hammer can build on Windows, an appveyor.yml and associated build scripts will build hammer and its examples. The idea is that as soon as the appveyor.yml exists in the repository, pull requests that would impede Windows portability would be immediately detected. The scripts expect CL.EXE to be in the path, and will produce their results in build/ The highest level of warning is enabled on CL.EXE, minus warnings that bring CL.EXE to a level that ressembles C99. The only notable warning that was disabled is the one that tells you about implicit truncating conversions. Hammer's source code has quite a few implicit conversions say from a 64bit unsigned integer to a integer of a lesser size (signed or otherwise)
2015-08-09 15:20:43 +02:00
desugar.c
glue.c
hammer.c
Update list of files to compile on windows
2015-08-16 16:20:53 +02:00
pprint.c
Finish porting hammer's library to windows We port registry by importing the (public domain) openbsd implementation of the tfind/tsearch POSIX binary tree search functions. These are only necessary when building on non-posix platforms
2016-01-31 17:27:19 +01:00
registry.c
Remove void pointer arithmetics in system_allocator.c We replace instances of void* w/ char* arithmetics. This allows system_allocator.c to be compiled with MSVC. Also we introduce a struct to represent the size_t header.
2015-08-16 09:10:04 +02:00
system_allocator.c
Finish porting hammer's library to windows We port registry by importing the (public domain) openbsd implementation of the tfind/tsearch POSIX binary tree search functions. These are only necessary when building on non-posix platforms
2016-01-31 17:27:19 +01:00
tsearch.c
windows build: Add build scripts + appveyor.yml In order to guarantee that Hammer can build on Windows, an appveyor.yml and associated build scripts will build hammer and its examples. The idea is that as soon as the appveyor.yml exists in the repository, pull requests that would impede Windows portability would be immediately detected. The scripts expect CL.EXE to be in the path, and will produce their results in build/ The highest level of warning is enabled on CL.EXE, minus warnings that bring CL.EXE to a level that ressembles C99. The only notable warning that was disabled is the one that tells you about implicit truncating conversions. Hammer's source code has quite a few implicit conversions say from a 64bit unsigned integer to a integer of a lesser size (signed or otherwise)
2015-08-09 15:20:43 +02:00
parsers/action.c
parsers/and.c
parsers/attr_bool.c
Add all remaining parsers that were not compiling on windows The last file to port for the library is registry.c
2015-12-13 14:58:23 +01:00
parsers/bind.c
parsers/bits.c
windows build: Add build scripts + appveyor.yml In order to guarantee that Hammer can build on Windows, an appveyor.yml and associated build scripts will build hammer and its examples. The idea is that as soon as the appveyor.yml exists in the repository, pull requests that would impede Windows portability would be immediately detected. The scripts expect CL.EXE to be in the path, and will produce their results in build/ The highest level of warning is enabled on CL.EXE, minus warnings that bring CL.EXE to a level that ressembles C99. The only notable warning that was disabled is the one that tells you about implicit truncating conversions. Hammer's source code has quite a few implicit conversions say from a 64bit unsigned integer to a integer of a lesser size (signed or otherwise)
2015-08-09 15:20:43 +02:00
parsers/butnot.c
parsers/ch.c
parsers/charset.c
Add all remaining parsers that were not compiling on windows The last file to port for the library is registry.c
2015-12-13 14:58:23 +01:00
parsers/choice.c
windows build: Add build scripts + appveyor.yml In order to guarantee that Hammer can build on Windows, an appveyor.yml and associated build scripts will build hammer and its examples. The idea is that as soon as the appveyor.yml exists in the repository, pull requests that would impede Windows portability would be immediately detected. The scripts expect CL.EXE to be in the path, and will produce their results in build/ The highest level of warning is enabled on CL.EXE, minus warnings that bring CL.EXE to a level that ressembles C99. The only notable warning that was disabled is the one that tells you about implicit truncating conversions. Hammer's source code has quite a few implicit conversions say from a 64bit unsigned integer to a integer of a lesser size (signed or otherwise)
2015-08-09 15:20:43 +02:00
parsers/difference.c
parsers/end.c
parsers/endianness.c
parsers/epsilon.c
parsers/ignore.c
parsers/ignoreseq.c
parsers/indirect.c
parsers/int_range.c
parsers/many.c
parsers/not.c
Add all remaining parsers that were not compiling on windows The last file to port for the library is registry.c
2015-12-13 14:58:23 +01:00
parsers/nothing.c
windows build: Add build scripts + appveyor.yml In order to guarantee that Hammer can build on Windows, an appveyor.yml and associated build scripts will build hammer and its examples. The idea is that as soon as the appveyor.yml exists in the repository, pull requests that would impede Windows portability would be immediately detected. The scripts expect CL.EXE to be in the path, and will produce their results in build/ The highest level of warning is enabled on CL.EXE, minus warnings that bring CL.EXE to a level that ressembles C99. The only notable warning that was disabled is the one that tells you about implicit truncating conversions. Hammer's source code has quite a few implicit conversions say from a 64bit unsigned integer to a integer of a lesser size (signed or otherwise)
2015-08-09 15:20:43 +02:00
parsers/optional.c
parsers/permutation.c
parsers/sequence.c
parsers/token.c
parsers/unimplemented.c
parsers/whitespace.c
parsers/xor.c
parsers/value.c
backends/packrat.c
backends/llk.c
Update list of files to compile on windows
2015-08-16 16:20:53 +02:00
backends/regex.c
windows build: Add build scripts + appveyor.yml In order to guarantee that Hammer can build on Windows, an appveyor.yml and associated build scripts will build hammer and its examples. The idea is that as soon as the appveyor.yml exists in the repository, pull requests that would impede Windows portability would be immediately detected. The scripts expect CL.EXE to be in the path, and will produce their results in build/ The highest level of warning is enabled on CL.EXE, minus warnings that bring CL.EXE to a level that ressembles C99. The only notable warning that was disabled is the one that tells you about implicit truncating conversions. Hammer's source code has quite a few implicit conversions say from a 64bit unsigned integer to a integer of a lesser size (signed or otherwise)
2015-08-09 15:20:43 +02:00
backends/glr.c
backends/lalr.c
backends/lr.c
backends/lr0.c
Reference in a new issue Copy permalink