Comments (5)
Great write-up, thank you. Your fix looks right to me from the plugin's perspective, but I wonder whether other things will now break given that Zeek itself also uses ConfigurePackaging
, and something should establish those directories. So we may need a way to distinguish the two uses, for example by relying on the fact that a plugin's cmake setup will source ZeekPlugin
. @0xxon likely knows this area best.
Also, I understand zkg is the way forward, but zkg is exclusively source focused requiring you to build source plugins on the target system (unless things have changed, bundle just tars up the source repos).
Yeah. Plus, we will keep supporting Zeek plugins (as opposed to Zeek packages that happen to include a plugin) as standalone entities. Some folks among our user base already package up their plugins as RPMs. They likely aren't using our binary packages, though, so this problem hasn't come up before.
from cmake.
The packages that we provide actually don't use make package
- I don't think we actively have used this for years. We instead manually create rpms/debs.
So - I actually have no clue about this part of the build system - it probably is not super well tested :)
from cmake.
And I have to admit I had no idea we have RPM-tailored content in our cmake setup. :-) The above PR keeps your approach, @Mraoul, and just guards it so it only kicks in when we're building a dynamic plugin.
from cmake.
The packaging setup code has been part of the plugin skeleton for a very long time and is being carried over into the zkg package template, but I wonder if I'm the only one who uses that functionality ^_^. I applied the diff/patch from #32 to my local install (still 4.0.1) and it worked as expected, so that looks like a fix to me.
Thanks!
from cmake.
I've bumped cmake in Zeek itself, since it installs the cmake modules. I've not bumped the cmake submodules in the various other repos, since it shouldn't make any difference for them. Holler if I'm overlooking something.
from cmake.
Related Issues (10)
- scripts not added through zeek_plugin_script are still added to packaging
- cmake policy warning CMP0110 HOT 1
- Plugin-level scripts install via symlink back into the source tree
- Remove vendored cmake files?
- zeek_add_plugin: No zeek_plugin_scripts() equivalent? HOT 4
- BifCl.cmake needs Zeek::BifCl triggered when touching CMakeLists.txt HOT 1
- Required compiler versions are out-of-date from Zeek documentation
- Consider installing Spicy grammars for bundled Spicy parsers
- Installing scripts is broken for Spicy analyzers. HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cmake.