use quill both in an app and it's depdant library

[samever7]

Hi there,
Like in the title, is there a way or a demo to show how to use quill both in an app and it's depdant library? If use shared library wrap for quill it's better.

I checked in the examples folder and not found one code file that demo this.

Any helps are welcome~
Thanks~

[odygrd]

Hey, it’s better to statically link. Assume you have an app main using underlying libs foo.a and bar.a.

1. You can define a global quill::Logger* that you extern and use in both libs. This doesn’t require to pass logger around but it’s little bit less flexible if you want to call same functions using different loggers.

2. You can pass a quill::Logger* to each of the lib classes or functions.

3. You can call quill::get_logger in the libs to retrieve an existing logger by name.

It really depends on your preference which approach you want to follow. Let me know which direction you're leaning towards and I can help with a more concrete example

[samever7]

Thank you odygrd for your quick response~
I prefer to use the 3rd way, quill::get_logger in the libs to retrieve logger, and a example will be more better for me to learn how to use it.
And by using this, is it a must to use statically link of quill?

[odygrd]

This is a simple example how to use it with either looking up a logger* or passing it around. Looking up the logger* each time is less efficient. It is better to store it or pass it around

https://github.com/odygrd/quill/tree/libexample/examples/libexample

Personally I prefer more to have a logger* (or multiple) stored globally and use that. I modified the recommended example so you can also have a look there (see FooGlobal)

https://github.com/odygrd/quill/tree/libexample/examples/recommended_usage

[samever7]

Thank you odygrd, it's fit for me~ Nice work~