================
@@ -0,0 +1,34 @@
+[build-system]
+requires = ["setuptools>=42", "setuptools_scm"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "clang"
+description = "libclang python bindings"
+readme = {file = "README.txt", content-type = "text/plain"}
+
+license = { text = "Apache-2.0 with LLVM exception" }
+authors = [
+ { name = "LLVM" }
+]
+keywords = ["llvm", "clang", "libclang"]
+classifiers = [
+ "Intended Audience :: Developers",
+ "License :: OSI Approved :: Apache Software License",
+ "Development Status :: 5 - Production/Stable",
+ "Topic :: Software Development :: Compilers",
+ "Operating System :: OS Independent",
+ "Programming Language :: Python :: 3",
+]
+dynamic = ["version"]
+
+[project.urls]
+Homepage = "http://clang.llvm.org/";
+Download = "http://llvm.org/releases/download.html";
----------------
nightlark wrote:
It looks like @sighingnow is the one who maintains that site (doc build scripts
at https://github.com/sighingnow/libclang/tree/master/docs). If he's okay with
it (my RTD username is rmast), I can get that documentation site updated.
Otherwise, the docs are just built with sphinx so we could upload it as a
subpage to one of the documentation sites under the llvm.org domain -- if the
source code for those sites is under the llvm org I can look at opening a PR to
generate the libclang Python binding docs and deploying them to a website.
https://github.com/llvm/llvm-project/pull/125806
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
