QuietMisdreavus
924936d042
Merge pull request #82 from incertum/chore/workflow-permissions
...
chore: remove unusued GitHub workflows
2025-10-17 11:12:33 -06:00
Melissa Kilby
fc2e337316
chore: remove unusued GitHub workflows
...
Signed-off-by: Melissa Kilby <mkilby@apple.com >
2025-10-13 13:04:28 -07:00
QuietMisdreavus
e02dcabc65
Merge pull request #81 from z2oh/gfm
...
Move `extensions/include/cmark-gfm-core-extensions.h` cpp includes out of extern "C" block
2025-09-08 16:09:11 -07:00
Jeremy Day
b11ff4736e
Move cpp includes out of extern "C" block
2025-08-22 11:50:55 -07:00
QuietMisdreavus
cbd8eae068
Merge pull request #75 from kkebo/wasm32-wasi
...
feat: add partial support for WASI
2025-08-05 11:16:35 -06:00
Kenta Kubo
415c3ac674
build: change CMARK_THREADING to 0 or 1
2025-04-03 00:13:50 +09:00
Kenta Kubo
0627c66d5f
Revert "build: hoist CMARK_THREADING to a build-only config"
...
This reverts commit aef4761a78
2025-04-03 00:13:50 +09:00
Kenta Kubo
1153b7f24e
Revert "remove empty config.h and cmark-gfm_config.h headers"
...
This reverts commit 6f648763b2
2025-04-03 00:13:49 +09:00
Kenta Kubo
ebf5f2b4bd
feat: add partial support for WASI
...
This change allows building the `cmark-gfm` target for both `wasm32-unknown-wasi` and `wasm32-unknown-wasip1-threads`. The other targets are not tested.
The differences between two target triples:
- `wasm32-unknown-wasi`
- C
- can import `unistd.h`
- has `__wasi__`
- does not have `__unix__`
- **does not have `_REENTRANT`**
- **does not have `_POSIX_THREADS`**
- **does not support pthreads API at all**
- Swift
- can use `#if os(WASI)`
- SwiftPM
- `BuildSettingsCondition`'s `Platform` is `.wasi`
- `wasm32-unknown-wasip1-threads`
- C
- can import `unistd.h`
- has `__wasi__`
- does not have `__unix__`
- **has `_REENTRANT` (defined in wasi-libc)**
- **has `_POSIX_THREADS` (defined in wasi-libc)**
- **supports a subset of pthreads API**
- Swift
- can use `#if os(WASI)`
- SwiftPM
- `BuildSettingsCondition`'s `Platform` is `.wasi`
2025-04-03 00:13:46 +09:00
QuietMisdreavus
b97d09472e
Merge pull request #77 from jmschonfeld/list-markers-api
...
Expose list marker characters for unordered lists
rdar://147511402
2025-04-01 11:09:55 -06:00
Jeremy Schonfeld
785b6f5480
Expose list marker characters for unordered lists
2025-03-20 13:29:46 -07:00
QuietMisdreavus
b022b08312
Merge pull request #58 from swiftlang/egorzhdan/include-inside-extern-c
...
NFC: Move `#include`s out of `extern "C"` block
2024-09-11 14:56:35 -06:00
Egor Zhdan
8a43e0a410
NFC: Move #includes out of extern "C" block
...
This fixes a clang compiler error when using these headers in C++ language mode:
```
libcmark_gfm/include/registry.h:8:1: error: import of C++ module 'libcmark_gfm' appears within extern "C" language linkage specification
#include "cmark-gfm.h"
```
rdar://109730567
2024-09-10 16:56:51 +01:00
QuietMisdreavus
fc07ab5da4
Merge pull request #73 from bc-lee/feature/pic
...
Build with Position Independent Code unconditionally
Fixes https://github.com/swiftlang/swift/issues/75216
2024-07-15 09:22:23 -06:00
Byoungchan Lee
936f6fde92
Build with Position Independent Code unconditionally
...
To avoid linking errors, build libcmark-gfm with Position Independent
Code unconditionally.
Related: https://github.com/swiftlang/swift/issues/75216
2024-07-13 06:56:16 +09:00
Saleem Abdulrasool
2c47322cb3
Merge pull request #72 from compnerd/config
...
build: add cmark-gfm-config to allow wiring up builds
2024-01-31 07:54:19 -08:00
Saleem Abdulrasool
7733c64aac
build: add cmark-gfm-config to allow wiring up builds
...
Enable wiring up builds with the staged image of cmark. The unified
build no longer tries to use custom build handling and instead prefers
the standard CMake usage.
2024-01-30 09:49:41 -08:00
Mishal Shah
9b50a73a7a
Merge pull request #71 from bnbarham/gnu-decls
2024-01-26 22:12:00 -08:00
Ben Barham
8c5c74b2f1
Add define for GNU glibc extensions
...
`fdopen`, `strdup`, and `mkstemp` are all extensions. `_DEFAULT_SOURCE`
should be enough for this, but apparently not on older glibcs.
2024-01-26 15:23:37 -08:00
Saleem Abdulrasool
6a97b58477
Merge pull request #70 from compnerd/include
...
build: include `include` in `INTERFACE_INCLUDE_DIRECTORIES`
2024-01-25 15:11:49 -08:00
Saleem Abdulrasool
8ddd2355be
build: include include in INTERFACE_INCLUDE_DIRECTORIES
...
This is require to build against the non-CONFIG form of the library.
2024-01-25 14:08:23 -08:00
Saleem Abdulrasool
595876bfe2
Merge pull request #69 from compnerd/swift-markdown-support
...
Swift markdown support
2024-01-24 14:40:21 -08:00
Saleem Abdulrasool
b59a9a3bac
build: cmark-gfm.h is not an umbrella header
...
This header does not cover all headers. Furthermore, it forces the
subsuming of `mutex.h` which is a private header. Fixing the module
definition to repair the macOS build.
2024-01-18 11:10:33 -08:00
Saleem Abdulrasool
ba667926a4
build: restore cmarkTargets.cmake for non-Windows targets
...
This file should be excised but retain it temporarily to allow us to
migrate away from the current build infrastructure.
2024-01-16 13:46:16 -08:00
Saleem Abdulrasool
33410d5a94
build: propagate the static define for Swift
...
When building a Swift target against this library we need to ensure that
we pass along `-DCMARK_GFM_STATIC_DEFINE` to the Clang Importer. This is
required to build SwiftFormat against this library statically.
2024-01-16 13:44:20 -08:00
Saleem Abdulrasool
c5d1389150
build: reorganise the build files
...
Shuffle the behaviour checks to the beginning of the processing.
Co-locate and hoist the options that the project supports, put custom
behavioural changes in a single location.
2024-01-05 09:27:17 -08:00
Saleem Abdulrasool
8aa6779901
build: remove generation of the version
...
We had drifted in the version management. Rather than risking the
divergence between CMake and SPM in the future, prefer to just have a
single manually maintained version of the version header.
2024-01-05 09:27:17 -08:00
Saleem Abdulrasool
6f648763b2
remove empty config.h and cmark-gfm_config.h headers
...
These no longer serve any purpose and allow us to remove them.
2024-01-05 09:27:17 -08:00
Saleem Abdulrasool
e049736252
remove mutex.h from the distribution
...
This header is an internal header and should not be exposed to the user.
This fully internalises the concept of thread safety to the build.
2024-01-05 09:27:17 -08:00
Saleem Abdulrasool
aef4761a78
build: hoist CMARK_THREADING to a build-only config
...
This macro does not impact the public API surface and the user should
not have to care. This removes the macro from the configuration headers.
2024-01-05 09:27:17 -08:00
Saleem Abdulrasool
c788cd0669
build: clean up the install rules
2024-01-05 09:27:17 -08:00
Saleem Abdulrasool
ebc53bf788
build: remove unnecessary include path handling
...
The includes are properly propagated by the targets, there is no need to
explicitly specify them.
2024-01-05 09:27:17 -08:00
Saleem Abdulrasool
b3a77541ee
build: simplify version handling
...
The SOVERSION was the same as the VERSION parameter, just use the same
parameter.
2024-01-05 09:27:17 -08:00
Saleem Abdulrasool
3b3b6e8b73
build: bulk set target properties
...
Avoid setting properties individually and set them in bulk. This avoids
unnecessary property computation in CMake.
2024-01-05 09:27:16 -08:00
Saleem Abdulrasool
7d6b9657a5
build: inline useless variables
...
Repetition is preferred. This aids in discoverability when working with
the build system.
2024-01-05 09:27:16 -08:00
Saleem Abdulrasool
a6a5db4b9b
build: remove extraneous variable definition
2024-01-05 09:27:16 -08:00
Saleem Abdulrasool
3c4fd90fc0
build: remove CMARK_SHARED and CMARK_STATIC
...
Prefer to use the standard `BUILD_SHARED_LIBS` option to control the
library type that we are building. Build a single instance of the
library. This allows for better control of the library usage in a larger
project. See the following blog post for the recommendation:
https://alexreinking.com/blog/building-a-dual-shared-and-static-library-with-cmake.html
2024-01-05 09:27:16 -08:00
Saleem Abdulrasool
8a5ffa01e9
build: prefer to use CMake to propagate include directories
2024-01-05 09:27:16 -08:00
Saleem Abdulrasool
bb3619e176
build: use CMAKE_INCLUDE_CURRENT_DIR
...
This uses the CMake mechanism for including the current source and
binary directories. This avoids the custom handling for this.
2024-01-05 09:27:16 -08:00
Saleem Abdulrasool
56fd1344df
build: remove unnecessary variables
...
Variables should be avoided. Repetition is not bad in this case. Inline
the single use variables.
2024-01-05 09:27:16 -08:00
Saleem Abdulrasool
403f409198
build: rely on CMake to drive thread linkage
...
This allows better control over POSIX or HP pthreads vs Solaris or
Windows threads. It also simplifies the configuration a little bit.
2024-01-05 09:27:15 -08:00
Saleem Abdulrasool
adab37db45
build: prefer the GNU install dirs uniformly
...
Use the GNU install dirs variables to control the install behaviour
rather than hardcoding the paths and tweaking the library directory
suffix.
2024-01-05 09:27:15 -08:00
Saleem Abdulrasool
845897ae67
build: permit incremental linking on Windows
...
This was introduced with the very first import of the CMake based build
system. There is no reason to disable it here, so just remove the
addition.
2024-01-05 09:27:15 -08:00
Saleem Abdulrasool
fa7f44118d
build: remove the use of generated export header
...
We have statically defined the header and use that in the SPM build
anyway. Avoid the generation and uniformly use the static header.
2024-01-05 09:27:15 -08:00
Saleem Abdulrasool
52348799ee
glob: don't glob the headers
...
Globbing does not help the build system - it does not know the files.
The glob is only performed at configure time, anything done after that
is not reflected in the build system. Just simply ignore the header
changes as it is pointless. Let the header scan capture the dependencies
if needed.
2024-01-05 09:27:15 -08:00
Saleem Abdulrasool
4fe1fd64f8
build: only build the fuzzer when appropriate
...
This is a test binary, only build it if testing is enabled.
2024-01-05 09:27:15 -08:00
Saleem Abdulrasool
8b51fc28d0
build: do not intrude upon the sanctity of the user flags
...
`CMAKE_C_FLAGS` should not be altered by the build configuration. Use
`add_compile_options`. Hoist the flags to the global level as these are
used globally. Support alternate C++ runtimes by using the C++ driver
rather than the C driver and specifying the C++ runtime by name. This
also fixes the bug where the C++ runtime library dependencies are
missed.
2024-01-05 09:27:15 -08:00
Saleem Abdulrasool
32f0f77276
build: protect the integrity of user variables
...
`CMAKE_C_FLAGS` are not available to the build system to modify, they
are strictly user controlled. Use `add_compile_options` to modify the
compile flags globally.
2024-01-05 09:27:15 -08:00
Saleem Abdulrasool
5c14e3b123
build: hoist profiling flags and debug macros up
...
This pulls the global configuration up to the top level. Avoid touching
the user controlled variables.
2024-01-05 09:27:14 -08:00
Saleem Abdulrasool
2e5584c1ee
build: clean up static define
...
`CMARK_GFM_EXTENSIONS_STATIC_DEFINE` is never used, remove it. Use CMake
to propagate `CMARK_GFM_STATIC_DEFINE` rather than defining it manually
and having the clients define it.
2024-01-05 09:27:14 -08:00
