Thread overview
importC and cmake
Sep 06, 2022
jmh530
Sep 07, 2022
zjh
Sep 07, 2022
jmh530
Sep 28, 2022
Chris Piker
Sep 28, 2022
zjh
Sep 29, 2022
Chris Piker
Sep 29, 2022
zjh
September 06, 2022

I was thinking about trying out importC with a library I have used in the past (it's been a few years since I used it with D). The library uses cmake to generate static or dynamic libraries (I believe I did static with Windows and dynamic with Linux, but I can't really recall).

My understanding of cmake is that it is used to generate the files needed to build something in a cross-platform kind of way (so make files for linux, project files for Visual studio, etc.). This doesn't seem consistent with how importC works (which would be using a D compiler to compile the project). I suppose I could just try it and see if it works, but since the project uses cmake I wonder if there aren't potentially things that cmake is doing that are important and could get missed in this naive sort of approach (for instance, it has a way to use algorithms written in C++ by default, though they can be disabled in the cmake file).

Does anyone have any importC experience with libraries that are built with a tool like cmake that could help make this clearer?

September 07, 2022

On Tuesday, 6 September 2022 at 19:44:23 UTC, jmh530 wrote:

>

.

xmake is simpler.

September 07, 2022

On Wednesday, 7 September 2022 at 00:31:53 UTC, zjh wrote:

>

On Tuesday, 6 September 2022 at 19:44:23 UTC, jmh530 wrote:

>

.

xmake is simpler.

Ok...but I didn't write the library so I can't exactly tell them to use xmake when they already use cmake.

September 28, 2022

On Wednesday, 7 September 2022 at 00:31:53 UTC, zjh wrote:

>

xmake is simpler.

Thanks for the recommendation. Was struggling with cmake for a dependent clib. Xmake is indeed simpler.

September 28, 2022

On Wednesday, 28 September 2022 at 05:29:41 UTC, Chris Piker wrote:

>

Xmake is indeed simpler.

Xmake is really nice!

September 29, 2022

On Wednesday, 28 September 2022 at 06:04:36 UTC, zjh wrote:

>

On Wednesday, 28 September 2022 at 05:29:41 UTC, Chris Piker wrote:

>

Xmake is indeed simpler.

Xmake is really nice!

zjh

Sorry to go off topic for a moment, but do you happen to know how to tell xmake that my project is C only, and thus it shouldn't add the /TP flag to cl.exe? The obvious statement:

set_languages("c99")

doesn't accomplish that task.

Thanks for the help,

September 29, 2022

On Thursday, 29 September 2022 at 20:56:50 UTC, Chris Piker wrote:

>
set_languages("c99")

Try:

add_cxflags or add_files("src/*.c") or
set_languages("c") or
set_languages("c11") .

or ,use -l to set language.

xmake create -l c -t static test