[
https://bro-tracker.atlassian.net/browse/BIT-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19304#comment-19304
]
Robin Sommer commented on BIT-1302:
-----------------------------------
Good point. I'll put this one my todo list for cleaning up the plugin code, I
need to work more on that Makefile skeleton anyways.
> configuration of dynamic Bro plugin easily desynchronizes with Bro's
> configuration
> ----------------------------------------------------------------------------------
>
> Key: BIT-1302
> URL: https://bro-tracker.atlassian.net/browse/BIT-1302
> Project: Bro Issue Tracker
> Issue Type: Problem
> Components: Bro, bro-aux
> Reporter: Jon Siwek
> Priority: Low
>
> Any way for a dynamic plugin to automatically detect Bro's CMakeCache.txt has
> been changed since the last time it did a "load_cache" so that it can re-run
> the CMake configuration process?
> Maybe a hacky way would be to force the top-level/skeleton Makefile of the
> plugin to always do a `./configure` or a `touch build/CMakeCache.txt`.
> The specific problem I ran in to was
> 1) do a plain `./configure` of Bro
> 2) configure/build a plugin (e.g. I was using btest/plugins/file-plugin)
> 3) change my mind and do a `./configure --enable-debug` of Bro.
> 4) (re)building the plugin still uses the original compiler flags inherited
> from Bro's CMakeCache, but it's really important that it be using the same
> debug flags. In this case not too bad to realize that ABI of the Val class
> depends on -DDEBUG, but was still pretty unique/subtle to trace the resulting
> crashes back to the difference in compile flags between Bro and the plugin.
--
This message was sent by Atlassian JIRA
(v6.4-OD-12-026#64007)
_______________________________________________
bro-dev mailing list
[email protected]
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
