summaryrefslogtreecommitdiffstats
path: root/qpb/subdir.am (follow)
Commit message (Collapse)AuthorAgeFilesLines
* mgmtd: Bringup MGMTD daemon and datastore module supportChristian Hopps2023-03-221-20/+0
| | | | | | | | | | | | | | | | | | | Features added in this commit: 1. Bringup/shutdown new management daemon 'mgmtd' along with FRR. 2. Support for Startup, Candidate and Running DBs. 3. Lock/Unlock DS feature using pthread lock. 4. Load config from a JSON file onto candidate DS. 5. Save config to a JSON file from running/candidate DS. 6. Dump candidate or running DS contents on the terminal or a file in JSON/XML format. 7. Maintaining commit history (Full rollback support to be added in future commits). 8. Addition of debug commands. Co-authored-by: Yash Ranjan <ranjany@vmware.com> Co-authored-by: Abhinay Ramesh <rabhinay@vmware.com> Co-authored-by: Ujwal P <ujwalp@vmware.com> Signed-off-by: Pushpasis Sarkar <pushpasis@gmail.com>
* build: fix `AM_LDFLAGS` usage (and gcov)David Lamparter2021-07-211-1/+1
| | | | | | | | | | | | | | | | like the other automake variables, setting `xyz_LDFLAGS` causes `AM_LDFLAGS` to be ignored for `xyz`. For some reason I had in my mind that automake doesn't do this for LDFLAGS, but... it does. (Which is consistent with `_CFLAGS` and co.) So, all the libraries and modules have been ignoring `AM_LDFLAGS` (which includes `SAN_FLAGS` too). Set up new `LIB_LDFLAGS` and `MODULE_LDFLAGS` to handle all of this correctly (and move these bits to a central location.) Fixes: #9034 Fixes: 0c4285d77eb ("build: properly split CFLAGS from AC_CFLAGS") Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
* build: fix assert() use in .pb-c.c filesDavid Lamparter2021-05-031-0/+1
| | | | | | | The .pb-c.c files pick up our assert() override, but that needs config.h to be included too, and that needs to go at the very top of the file... Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
* build: fix protobuf out-of-tree buildDavid Lamparter2021-04-211-2/+2
| | | | | | | Otherwise it aborts with "File does not reside within any path specified using --proto_path (or -I)" Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
* build: add LLVM bitcode targetsDavid Lamparter2020-05-051-0/+1
| | | | | | | Just an easy way to produce LLVM .bc (bitcode) files. Not used during normal builds. Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
* build: fix "make tags"David Lamparter2019-09-171-0/+3
| | | | | | | | | | | Anything we list in a xxx_SOURCES variable will be included for "make tags", including filess marked as nodist_xxx_SOURCES. So if we don't have Protobuf enabled, even though the entire library isn't built, "make tags" will still try to process these files... which we can't autogenerate because Protobuf is disabled. Same for gRPC. Fixes: #3266 Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
* build: clean up protobuf build integrationDavid Lamparter2018-09-081-27/+12
| | | | | | | We were linking all libs and binaries against libprotobuf-c if the option was enabled... that makes no sense at all. Signed-off-by: David Lamparter <equinox@diac24.net>
* build: remove common.amDavid Lamparter2018-09-081-0/+36
| | | | | | Fold things into where they make sense. Signed-off-by: David Lamparter <equinox@diac24.net>
* build: clean up BUILT_SOURCESDavid Lamparter2017-08-041-1/+0
| | | | | | | | | | | | | | | BUILT_SOURCES doesn't do what the name suggests. What it actually means is "these files should be built first when doing a 'make' without explicit target" (or "make all"). It's pretty much almost always wrong to use BUILT_SOURCES, the only correct use is when a file is needed by an unspecified / large set of files. Also remove version.h and route_types.h from dist tarball while we're at it. configure will create them anyway. Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
* build: non-recursive qpb & fpmDavid Lamparter2017-07-311-0/+26
Signed-off-by: David Lamparter <equinox@opensourcerouting.org>