Correct or idiomatic way to use local c code that I don't want to add janet code to

[krsanky]

I have a C module I wrote config.h and config.c.
I want to call this from my janet C code.
How do I tell jpm about my config.o module ?
Or where should I put it?

The point is I would prefer not to add any janet code
to the module so I can use it as is from my other c projects
as well.

If I was doing plain C code I would add paths to my Makefile like:
CFLAGS+= -I$(HOME)/code/config
LDFLAGS+= -L$(HOME)/code/config

[sogaiu]

In janet-pcg-random there is a file named pcg_random.c (that has Janet bits) which makes use of code from the pcg-c directory tree (which has .c and .h files that don't reference any Janet C code).

May be that's close to the situation you described?

FWIW, the corresponding project.janet looks like this ATM:

(declare-project
  :name "pcgrand"
  :description "Janet bindings for PCG Random"
  :url "https://github.com/sogaiu/janet-pcg-random"
  :repo "git+https://github.com/sogaiu/janet-pcg-random")

(declare-native
  :name "pcgrand"
  :cflags   [;default-cflags
             "-Ipcg-c/include"
             "-std=c99" "-Wall" "-Wextra"]
  :headers ["pcg-c/include/pcg_variants.h"]
  :source ["pcg-c/src/pcg-advance-32.c"
           "pcg_random.c"])

[krsanky]

Awesome, Thanks!!!!
This sounds like what I am trying to do.
I think part of it is that I just need to level up in basic Janet project usage.