Page MenuHomeFreeBSD

[privatelib] install libevent1 and sqlite3 headers to faciliate base tool development I'd like to use the in-system private libevent1 and sqlite3 headers to faciliate new base tools. Since libevent1 is pretty small compared to libevent2, I would...
ClosedPublic

Authored by adrian on Mar 23 2017, 7:13 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Nov 18, 5:21 PM
Unknown Object (File)
Oct 23 2024, 7:40 PM
Unknown Object (File)
Oct 22 2024, 9:48 PM
Unknown Object (File)
Oct 22 2024, 9:48 PM
Unknown Object (File)
Oct 22 2024, 9:48 PM
Unknown Object (File)
Oct 22 2024, 9:47 PM
Unknown Object (File)
Oct 22 2024, 9:27 PM
Unknown Object (File)
Sep 23 2024, 1:29 AM

Details

Summary

...also like to eventually look at migrating the various versions of cooked-up
event IO loops, signal handling, etc into using our libvent1 library version.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

I don't quite understand your reasoning. Are you wanting to use these for your own purposes or for actually developing something that is *in tree*? If it is in-tree, then I can explain a process to use that will make this not needed.

Well, I'd also like to cross build some stuff that's external (like tools/tools/ath/) too. This is done for ucl, which makes it easy to include that.

bdrewery added inline comments.
lib/libevent/Makefile
13 ↗(On Diff #26618)

This line serves no purpose, might as well remove it in lieu of adding INCS.

This revision now requires changes to proceed.Mar 23 2017, 7:33 PM
adrian edited edge metadata.

Updating D10123: [privatelib] install libevent1 and sqlite3 headers to faciliate base tool development

I'd like to use the in-system private libevent1 and sqlite3 headers to faciliate
new base tools. Since libevent1 is pretty small compared to libevent2, I would...

Seems ok to me at quick glance, I would anyway go to a provite libevent2 in second steps rather than libevent1, performance are way better in libevent2 and given we would keep it private we could decide to only build what we need if size matters.

hi!

libevent2 is .. very big compared to the footprint of libevent1, even the base. If someone wants to do it as a separate pass and show we can get the size down to libevent1 size, then great. :)

This revision is now accepted and ready to land.Mar 27 2017, 9:36 PM
This revision was automatically updated to reflect the committed changes.

hi!

libevent2 is .. very big compared to the footprint of libevent1, even the base. If someone wants to do it as a separate pass and show we can get the size down to libevent1 size, then great. :)

we already have libevent2 in base - contrib/ntp/sntp/libevent