I think I've found an answer myself.
The key is having multiple cgi directories configured on the webserver, using
the ScriptAlias directive, one for each 'product' and then putting (or using a
symlink) a copy of the doxysearch.cgi binary in each one along with the product
specific search database. Then you need some way (script) to manipulate the
Doxyfile for each component, for example to insert the correct SEARCHENGINE_URL
setting when building the components documentation.
Keith
Hi,
We're playing around with using the External Indexing and Searching facility of
Doxygen, and have a question regarding the doxysearch.db generation and usage.
What we would ideally like (I think) is the ability to have multiple
doxysearch.db files, one per product (version). So for example:
Product A-1.0 depends on Library foo-1.0 and Library bar-1.0
Product B-2.0 depends on Library foo-2.0 and Library qux-2.2
For Product A there would be a doxysearch-A-1.0.db, and for Product B a
doxysearch-B-2.0.db (using the Multi project index method of generating the
db). These would need to live 'somewhere' on the webserver, and the right one
chosen depending on what Product/Library (with version) was being accessed.
Is this currently possible? Apologies if some of this is webserver
configuration related, but I'm a bit of a novice with webservers!
Keith
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users
