1
0
mirror of https://github.com/MariaDB/server.git synced 2026-10-23 18:49:29 +03:00
Files
mariadb/include
Sergei Golubchik 3977a282b7 MDEV-40608 MariaDB-devel is incomplete for plugins
This works on Linux and on Windows, with rpm/deb/tar.gz/zip
installations.

For rpm/deb it just works, for tar.gz/zip there is no
standard location, so one needs to configure plugin with

  -DCMAKE_PREFIX_PATH=/pah/to/mariadb/basedir

after that, `cmake --install .` works too, installing in the same
basedir.

`cmake --build . --target package` works, creating rpm/deb/targz/zip
depending on whether it's Linux or Windows and whether -DRPM or -DDEB
was specified.

* create and install mariadb-plugin-config.cmake
* for now it only supports one plugin per project, error out
  if there are many
* deb: move all headers that plugins need to libmariadb-dev,
  together with libmysqlservices.a. At least until we'll
  create mariadb-plugin-dev. Nobody should need huge
  libmariadbd-dev to develop a plugin
* rpm: all in MariaDB-devel already, no changes here
* install wsrep headers too, THD layout depends on WITH_WSREP
* show DBUG_OFF, ENABLED_DEBUG_SYNC, and SAFE_MUTEX to plugins, same
  reason (it doesn't happen automatically as they're not in my_config.h)
* but don't install config.h - high chance of name conflict with other
  projects and it's an exact copy of my_config.h anyway.
* adjust plugin.cmake to work for external plugins
* move server-internal part of it to top-level CMakeLists.txt
* remove double-defined macros from unireg.h (the guard doesn't help
  if unireg.h is included first)
* package plugin metadata as yaml in .tar.gz/.zip

ColumnStore, until fixed, needs a backward-compatibility workaround
2026-09-25 11:28:53 +02:00
..
2026-06-15 12:50:45 +02:00
2022-02-09 19:13:52 +01:00
2022-01-21 16:02:34 +01:00
2024-11-29 13:43:17 +02:00
2025-11-11 10:29:45 +02:00
2026-08-19 08:40:05 +02:00
2026-07-28 13:14:38 +02:00
2023-01-03 17:08:42 +02:00
2020-06-19 19:43:07 +02:00
2023-12-18 11:19:04 +01:00
2023-04-24 12:43:47 +02:00
2023-02-10 13:03:01 +02:00
2026-03-11 14:18:49 +02:00
2024-03-28 09:16:57 +02:00
2023-11-08 17:09:44 +01:00
2023-07-26 15:13:43 +03:00
2026-07-24 17:06:39 +02:00
2022-12-20 08:55:48 +11:00
2023-01-04 14:52:25 +02:00
2023-02-10 12:59:36 +02:00
2026-08-19 08:40:05 +02:00
…
…
2025-06-17 09:50:22 +02:00
2022-07-31 14:54:37 +02:00
2026-08-19 08:40:05 +02:00
…
…
2024-12-02 11:35:34 +02:00
2025-09-04 18:08:39 +03:00
2026-07-28 13:14:38 +02:00
2020-10-29 13:38:38 +02:00
2023-02-10 10:45:25 +01:00
…
2020-03-10 19:24:22 +01:00
2020-03-10 19:24:22 +01:00
2020-03-10 19:24:22 +01:00
2020-03-10 19:24:22 +01:00
2020-03-10 19:24:22 +01:00
2020-03-10 19:24:22 +01:00
2020-03-10 19:24:22 +01:00
…
2023-08-15 10:16:12 +02:00
2022-12-20 08:55:48 +11:00
…