| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
| |
CMake 3.21.4 reports that compatibility with CMake < 2.8.12 will be
removed from a future version of CMake.
CMake 3.0 has new defaults for MACOSX_RPATH. It seems ledger works fine
with them. See CMake Policy CMP0042 for the details.
|
|
|
|
|
|
|
| |
Windows uses UTF-16 for command line arguments, so use boost::nowide
to convert to UTF-8.
Fixes #1986
|
|
|
|
|
|
|
|
| |
Backported python cmake module expects at least cmake 3.7 (requested
by policy), which will break builds on older cmake versions, like 3.5.
This fix will omit python module inclusion for any cmake version less
than 3.7 and the build will continue without problems.
|
| |
|
| |
|
|
|
|
|
| |
Avoid needing to keep our copy updated and only keep it as a fallback
for when system cmake is not new enough.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On macOS, CMake detects the Boost.Python component installed by
homebrew only when named "python27". Thus this change not only adds a
Travis CI setup for macOS, but also a CMake option to switch the
component name between "python" and "python27". In addition,
precompiling system.hh does not work with the current setup for Clang,
so another CMake option to disable it is added.
The currently used commands to compile specific versions of Boost do
not produce a result that works out of the box on macOS. It should be
possible just to mimic homebrew's formula for boost-python
(https://github.com/Homebrew/homebrew-core/blob/master/Formula/boost-python.rb),
but for the moment on macOS this change tests only against Boost
installed by homebrew.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
CMAKE_CXX_COMPILER is the path to the compiler binary and does not
need to follow a specific pattern. For example, on Linux with GCC and
without an explicit "-DCMAKE_CXX_COMPILER:PATH=" option,
CMAKE_CXX_COMPILER is "/usr/bin/c++" which does not match "g++".
CMAKE_CXX_COMPILER_ID however will always reliably be "Clang" or
"GNU".
|
| | |
|
| |
| |
| |
| | |
macOS seems to be the current name for Mac OS X.
|
|/ |
|
| |
|
| |
|
|
|
|
| |
[ci skip]
|
| |
|
|
|
|
| |
[ci skip]
|
| |
|
| |
|
|
|
| |
when using version 1.59.0
|
|
|
|
| |
so that the tests run with a consistent environment.
|
|\
| |
| | |
Replace utfcpp submodule with partial subtree
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
it will look for utfcpp in the standard system paths, UTFCPP_PATH,
and lib/utfcpp/v2_0/source.
This allows the use of utfcpp in:
* standard locations such as /usr/include on distributions shipping
utfcpp
* custom locations for users via UTFCPP_PATH
* the source tree using the default location of the utfcpp
git submodule, .i.e lib/utfcpp/v2_0
Signed-off-by: Alexis Hildebrandt <afh@surryhill.net>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Remove utfcpp submodule
* Squashed 'lib/utfcpp/' content from commit 63cd498
git-subtree-dir: lib/utfcpp
git-subtree-split: 63cd4984464e875546b4a91918be7355357a3a68
* Merge commit '82003f30ba8ba436cf7cef380155f50ed4242b37' as 'lib/utfcpp'
* Remove needless utfcpp subtree files
* Change include path to utfcpp
Signed-off-by: Alexis Hildebrandt <afh@surryhill.net>
|
| |
| |
| |
| |
| |
| | |
APPLE and CMAKE_HOST_APPLE only check the host system,
whereas CMAKE_SYSTEM_NAME checks the target system when
cross-compiling.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Use -undefined dynamic_lookup to allow Python symbols to be discovered
when the ledger module is imported instead of at build time. Without
this change, the Python interpreter crashes when ledger is imported from
a python that is different from (but compatible with) the python against
which the module was built.
|
|/
|
|
| |
Bump version to 3.1.1-alpha.1
|
|
|
|
|
|
|
|
| |
The LICENSE.rtf file can be generated from LICENSE.md easily if needed,
at the moment there seems to be no use for it, since CPack isn't used
to generate binary distribution archives.
Signed-off-by: Alexis Hildebrandt <afh@surryhill.net>
|
|
|
|
| |
the same as the default CPack source generator
|
|
|
|
|
|
| |
Currently the path to install the python library in is determined by
running the python interpreter. We do not want to end up installing a
library built for python2 in the python3 library path!
|
| |
|
|\
| |
| | |
automating ledger build on Cygwin
|
| | |
|
|/
|
|
|
|
|
|
| |
http://bugs.ledger-cli.org/show_bug.cgi?id=985
Fix compilation issue on Cygwin by adding the '-U__STRICT_ANSI__' flag
to GCC. This avoids GCC disabling some stdlib functions like 'setenv'
and 'popen'.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to remove the warning below when running cmake.
In the long run changing the CMake rules to set MACOSX_RPATH
might be the better option.
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:
libledger
This warning is for project developers. Use -Wno-dev to suppress it.
|
|
|
|
|
|
|
|
|
|
|
| |
If set, the COLUMNS environment variable will take precedence over terminal
width. However, please note that COLUMNS is usually *not* exported by shells to
child processes, so in most cases COLUMNS will be undefined for ledger---hence
the motivation for this change.
Terminal width is queried using ioctl() on stdin. For the sake of portability
the querying is done only on platform where ioctl() is detected as supported at
compile-time.
|
| |
|
| |
|
|
|
|
|
| |
Add a space between if and the opening bracket, between a closing
round bracket and the following opening curly bracket, etc.
|
|
|
|
| |
I successfully compiled ledger with boost 1.49.0 on Debian 7.5.
|
| |
|
|
|
|
| |
since a separate acprep make doc is necessary to build the documentation
|
| |
|