On Thursday, 29 September 2022 at 20:56:50 UTC, Chris Piker wrote:
```lua
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.
```cpp
xmake create -l c -t static test
```
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 onl
On Wednesday, 28 September 2022 at 05:29:41 UTC, Chris Piker
wrote:
`Xmake` is indeed simpler.
`Xmake` is really nice!
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.
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.
On Tuesday, 6 September 2022 at 19:44:23 UTC, jmh530 wrote:
.
`xmake` is simpler.
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 understandi