With CTest it's much easier to run the tests via command line -
no need to specify path to compiler, etc. Simply run this command
(from the build directory):
ctest -C Debug
or
ctest -C Debug -R pcode.*
to run tests matching a regexp (it will run pcode_test_example in
this case)).
It is still possible to use the run_tests.py script directly.
* debug info for index tagmm warnings
This commit makes the compiler display debug information for "index" tag mismatch warnings.
* Fix#317
* Partially revert #c325ca3e028388ae6f934df2a4057229d24d021e to strip spaces in strings again.
* Redetect error 49, and make `deprecated` auto-insert spaces.
* Allow line continuations in single-line comments only when they are followed by another comment:
It is quite annoying to get an error for commenting out a define using:
//
// #define LONG_MACRO\
// did span \
// multiple lines
//
* v3.10.8
* Remove multi-line comment test.
* Fix test 217 again...
* Yet again fixing the tests...
* Cast error on mac.
* Release 3.10.8
* Sorry for messing up the commit history... I'm trying to figure out releases.
https://msdn.microsoft.com/en-us/library/0d294k5z.aspx
It looks like we don't need it. The 'char' type is signed on other
platforms, so why should it be unsigned on Windows? Besides, its
includion in add_definitions() prevented RC from compiling libpawn.rc
with Visual Studio 2017's CMake tools.
* Allow line continuation in single line comments
Other languages allow this:
// this is totally a single \
line comment
For example C++, at least GCC, Visual C++. I don't see why it
should be forbidden.
* Don't insert \a symbols to mark
Because we now don't need to check if there are '\\' in comments
we no longer have to mark their positions with '\a' symbols.
* Don't trim leading space after '\\'
Again, this is how other languages do it and it seems to be more
intuitive. If you don't want spaces just don't indent your lines.
new s[] = "see \
this?"
CMake Warning (dev):
Policy CMP0042 is not set: MACOSX_RPATH is enabled by default. Run "cmake
--help-policy CMP0042" for policy details. Use the cmake_policy command to
set the policy and suppress this warning.
MACOSX_RPATH is not specified for the following targets:
pawnc
This warning is for project developers. Use -Wno-dev to suppress it.
We don't need the whole AMX in order to compile pawndisasm, only a handful of
alignment functions (amx_AlignXXX) that are used in amxdbg.c. Just copy those
functions to amxdbg.
As a bonus, we don't have to fix compile warnings in amx.c now. (maybe somebody
will fix them some day in a distant future...)
__PawnBuild holds the currnt build number. This allows you to detect
which compiler version is used more precisely.
It will be set to 1 on next release and incremented on each subsequent
release.
Closes#132.
Now it's possible to run 'make install' to install binaries on your
system.
This also should resolve the deafult.inc & rpath problem (#54) as
CMake seems to remove rpath from binaries during installation.
This removes all scpack-packed strings and moves normal strings from
.scp files to corresponding .c files. The code responding for packing
and unpacking is gone as well.
If you have enough memory to run a SA-MP server you most likely have
more than enough of it to not worry about saving a few additional KBs
of text. Besides, these strings were kind of hard to navigate / edit,
and you could easily forget to regenerate them with scpack (though it
could be automated).
check_function_exists() tried to use a C++ compiler for some odd reason,
so I've set the language to C explicitly. This shouldn't hurt in theory,
since we don't use C++.
http://msdn.microsoft.com/en-us/library/0d294k5z.aspx
/J (Default char Type Is unsigned)
Changes the default char type from signed char to unsigned char, and
the char type is zero-extended when it is widened to an int type.
