2358570f2d
Remove static ( #90 )
2025-10-23 11:37:57 +03:00
02ec362f5c
Complete python3 fixes for issue #67
2025-07-03 08:55:00 -04:00
4b8160057a
Fix scripts to add python3 support
...
* fixed libraries include
* fixed incorrect usage of python2 string
* fixed python2 to python3 script issues (2to3) like print ""
* fixed data types
* fixed python3 usage of str instead of string (join, split etc.)
* added support to determine the absolute path of the executable
binary of the current Python interpreter
* thx @Bagira80 for his support
Fixes issue: #67
Signed-off-by: Thomas Höhlig <thoehlig@benocs.com >
2025-07-02 23:52:03 -04:00
03869de68e
Implement reusable Boost.CI workflow for GHA
2025-07-02 22:09:37 -04:00
74d927f984
Update ci.yml
2025-06-27 02:27:08 +03:00
aa3b1c464d
Condition macro workarounds on _MSC_EXTENSIONS instead of _MSC_VER. Fixes #84 .
2025-06-27 02:10:14 +03:00
7df84b35eb
Add a test for the conflict with <ciso646> under MSVC. Refs #84 .
2025-06-26 22:33:18 +03:00
cd74f40d46
Fix BOOST_MPL_AUX_ASSERT_NOT_NA
2025-01-03 15:32:30 -05:00
502078c91d
Do not check the birand/bitor macros in cplusplus mode
...
Some 3rdparty parsers (e.g. Qt moc) fail to parse the bitand.hpp
due to the fact that bitand is a keyword in C++, not a macro.
Modern MSVC versions define bitand/bitor only if __cplusplus macro
is not defined, see iso646.h: https://pastebin.com/zTcd0juT
Thus, boost can also check the macro only in C mode making moc happy
2025-01-03 11:34:47 -05:00
2b7937ac6f
Run char and integral_c tests with -funsigned-char
2025-01-03 12:34:15 +00:00
6172029f82
Update CI to 2024.12 spec, update README
2025-01-03 12:32:55 +00:00
d223d3cd60
Work around warnings in char.cpp and integral_c.cpp when char is unsigned. Fixes #50 .
2025-01-02 16:43:59 +02:00
bace27426e
Add a CI job testing -funsigned-char
2025-01-02 16:33:25 +02:00
c8a1f64ff6
Apply Node20 workaround
2025-01-02 16:06:34 +02:00
4b34fa1378
Update ci.yml
2025-01-02 16:05:45 +02:00
bf4a5afb3c
Add support for modular build structure. ( #79 )
...
* Make the library modular usable.
* Switch to library requirements instead of source. As source puts extra source in install targets.
* Add requires-b2 check to top-level build file.
* Bump B2 require to 5.2
* Change all <source> references to <library>.
* Update copyright dates.
* Move inter-lib dependencies to a project variable and into the build targets.
* Update build deps.
2024-11-30 17:11:24 -05:00
b37b709cbd
Merge branch 'next-prior' of https://github.com/ecatmur/mpl into feature/issue-69
2024-06-18 02:34:39 +03:00
b86c4cc950
Add test for issue #69
2024-06-18 02:23:56 +03:00
8b6fae5089
Add cmake_install_test, cmake_subdir_test
2024-06-17 22:50:05 +03:00
1856fa8429
Add test/CMakeLists.txt
2024-06-17 22:41:25 +03:00
271dea60f5
Update test/Jamfile.v2
2024-06-17 22:32:45 +03:00
992a85f466
Regenerate CMakeLists.txt
2024-06-17 22:30:26 +03:00
12a59d801f
Rewrite ci.yml
2024-06-17 22:25:12 +03:00
d4e911ab88
Do not try to install libpython-dev
2024-06-17 21:18:23 +03:00
1019bb5fad
Disable for_each.cpp under C++03
2024-06-17 21:17:39 +03:00
e30c4102a2
Update ci.yml
2024-06-17 21:06:03 +03:00
fb6b861834
Update integral_wrapper.hpp
...
Apply change since C++11
2023-11-27 09:55:00 -06:00
8499ae7e4f
Use static const for next/prior from C++17
...
Trying to form next/prior in constant evaluation may be ill-formed; see https://github.com/boostorg/mpl/issues/69
2023-11-24 08:53:05 -07:00
b440c45c28
Avoid Wzero-as-null-pointer-constant warning ( #75 )
...
Newer compilers may warn when using `0`, e.g.:
```
./boost/iterator/detail/facade_iterator_category.hpp:161:5: error: zero as null pointer constant [-Werror,-Wzero-as-null-pointer-constant]
BOOST_MPL_ASSERT_NOT((is_iterator_category<Traversal>));
^
./boost/mpl/assert.hpp:324:58: note: expanded from macro 'BOOST_MPL_ASSERT_NOT'
boost::mpl::assert_not_arg( (void (*) pred)0, 1 ) \
```
2023-05-10 21:16:45 -06:00
db09fb1dce
Fix ccache saving on cache hit ( #66 )
...
See boostorg/boost-ci#166
2022-06-24 08:57:36 -07:00
8f10d06b96
Fix unused variable warning from BOOST_MPL_ASSERT_* on Clang
2022-05-01 17:23:44 -04:00
03d89ec586
Fixes issue https://github.com/boostorg/mpl/issues/46
2022-05-01 16:07:58 -04:00
3301d917dc
Disable bigendian CI build to eliminate PR check failure for #50
2022-05-01 08:47:52 -04:00
bd4ec497a8
Use BOOST_WORKAROUND when checking compiler level
2022-05-01 08:47:52 -04:00
4634ef904e
Fix -Wparentheses warning not ignored on NVCC
...
BOOST_GCC is not defined for NVCC, therefore we should use BOOST_GCC_VERSION.
2022-05-01 08:47:52 -04:00
c61b1e3508
Fix some -Wsign-conversion warnings
2022-04-30 22:45:39 -04:00
e9e3faf4be
Align to Boost.CI 2022.04
2022-04-30 17:31:53 -04:00
5f79900dcc
Fix some XML validation errors ( #60 )
...
Relates #59
2021-12-01 19:37:28 -08:00
793bf12d42
Update GitHub Actions CI file ( #58 )
2021-08-04 07:03:02 -07:00
341748e4cb
Update CMakeLists.txt
2021-06-10 00:54:16 +03:00
db132085b9
Add GitHub Actions config [ci skip] ( #56 )
2021-03-03 18:30:05 -08:00
f3464e3ef7
add drone config [ci skip] ( #54 )
2021-02-25 12:02:20 -05:00
71ee3ac5bd
[skip ci] Add "cxxstd" json field. The "cxxstd" json field is being added to each Boost library's meta json information for libraries in order to specify the minumum C++ standard compilation level. The value of this field matches one of the values for 'cxxstd' in Boost.Build. The purpose of doing this is to provide information for the Boost website documentation for each library which will specify the minimum C++ standard compilation that an end-user must employ in order to use the particular library. This will aid end-users who want to know if they can successfully use a Boost library based on their C++ compiler's compilation level, without having to search the library's documentation to find this out. ( #55 )
2021-01-20 15:39:33 -05:00
cc883aa12a
Address model for msvc-10 and msvc-11 must be only 32-bit in appveyor.yml ( #53 )
2020-09-25 15:15:05 -04:00
6704b09dcf
It normally should not be necessary to use the _Z form of the BOOST_P… ( #52 )
...
* It normally should not be necessary to use the _Z form of the BOOST_PP_ENUM macro, although it is perfectly legal and helpful to do so, but in this case it is necessary as a workaround for a bug in the new VC++ standard conforming preprocessor. The bug manifests itself when testing the TTI library, which internally uses the Boost MPL code. The bug in the new VC++ standard conforming compiler is fixed in the VS2019 preview product, so that fix is sure to find its way to the official VS2019 product sometime soon. In the meantime this "fix" shortens the macro expansion somewhat and, while it should not be necessary, is still helpful.
* Fix for appveyor.yml file
* Added VS2019 tests, also with new preprocessor. Further MPL Fixes for new preprocessor bug, which are also useful and will speed up preprocessing.
* Can't seem to test msvc-10.0 or msvc-11.0 any more with Appveyor
* Update description
2020-09-24 06:07:26 -04:00
9c0f98f088
Fix invalid XHTML markup ( #51 )
2020-08-05 08:57:41 -07:00
3d8a60ed6a
Change __BORLANDC__ to BOOST_BORLANDC, which is defined in Boost config for the Embarcadero non-clang-based compilers. ( #48 )
...
Co-authored-by: Edward Diener <eldlistmailingz@tropicsoft.com >
2020-04-12 09:48:24 -07:00
e01a10925d
Replace three links that seem broken (keep timing out)
...
Fix broken sgi/stl links.
Fix broken gmane link.
2019-04-24 05:47:07 +10:00
273db79266
[CMake] Update formatting and add copy right note
2019-02-13 19:06:08 -05:00
c7df450a81
[CMake] Generate cmake target that other libraries can use
...
... to express their dependency on this library and retrieve any
configuration information such as the include directory, binary
to link to (if any), transitive dependencies, necessary compiler
options or the required c++ standards level.
2019-02-13 19:06:08 -05:00
Sergey Chebotarev
James E. King III
Thomas Höhlig
Peter Dimov
aihao1007
Ivan Komissarov
Jim King
René Ferdinand Rivera Morell
Ed Catmur
Alexander Grund
Nikita Kniazev
Mat Berchtold
Anis Ladram
Ion Gaztañaga
Jonathan Wakely
Sam Darwin
Edward Diener
Jonathan Wakely
Edward Diener
tinko92
Mike Dev