Generated schema source code is not compiled in #40

New issue

Closed

opened 2023-11-02 20:19:20 +00:00 by lda · 1 comment

lda commented

2023-11-02 20:19:20 +00:00

Contributor

Type

Other

Description

Right now, if you try building Telodendria simply, you will get an error saying that make doesn't have a rule for a generated piece of source code.

After some looking around, it seems like the ./configure script doesn't add those generated schemas onto the Makefile.

Log Output

```
[building Telodendria]
make: *** No rule to make target 'build/Schema/ClientEvent.o', needed by 'out/bin/telodendria'.  Stop.
```

### Type Other ### Description Right now, if you try building Telodendria simply, you will get an error saying that `make` doesn't have a rule for a generated piece of source code. After some looking around, it seems like the `./configure` script **doesn't** add those generated schemas onto the Makefile. ### Log Output ````shell ``` [building Telodendria] make: *** No rule to make target 'build/Schema/ClientEvent.o', needed by 'out/bin/telodendria'. Stop. ``` ````

jordan added the

bug

label 2023-11-03 13:36:26 +00:00

jordan added this to the Telodendria v1.7.0-alpha4 project 2023-11-03 13:36:29 +00:00

jordan self-assigned this 2023-11-03 13:36:34 +00:00

jordan started working 2023-11-04 18:45:23 +00:00

jordan commented

2023-11-04 19:03:46 +00:00

Owner

I'm going to try to re-work the way the schema sources are generated. They should not be in the source tree, they should be put in build/ since they are generated, even though they are C source files. With the custom build script, the source tree was scanned on every invocation, so it wasn't a big deal, and I put them in src/ as a shortcut. However, the source tree is only scanned when configure is run, not on every build, which is what's causing this.

I'm going to try to re-work the way the schema sources are generated. They should not be in the source tree, they should be put in `build/` since they are generated, even though they are C source files. With the custom build script, the source tree was scanned on every invocation, so it wasn't a big deal, and I put them in `src/` as a shortcut. However, the source tree is only scanned when `configure` is run, not on every build, which is what's causing this.

jordan referenced this issue from a commit

2023-11-04 19:28:15 +00:00

Schema are now generated out-of-tree.

jordan closed this issue

2023-11-04 19:28:16 +00:00

jordan stopped working 2023-11-04 19:28:16 +00:00

42 minutes 53 seconds