On 29/11/2010, at 18:25, Julian Pietron wrote: >> The easiest way to get the whole thing to work is to pass the following >> parameters to configure: >> >> --enable-static-module=all >> --enable-static >> --enable-shared=no > > as you can see in my initial post, I tried to compile statically after > my first attempt with shared libraries failed. > I guess, compilation worked, because it resulted in a cherokee-worker > that was approx. 1MB of size compared to a cherokee-worker compiled > dynamically which only had around 50kB. > But I ran into the problem I mentioned above: cherokee still claimed > that it could not load the wildcard plugin (which should've been > compiled in as I used --enable-static as you stated above and the build > system also produced static libraries for each of the plugins > contained), and I'm sure that, if the wildcard plugin was found, it > would've failed on loading any of the other plugins as well.
I don't think Automake linked those plug-in files, actually. The --enable-static-module parameter modified the logic of the compilation (it is more than just '--enable-static'). It looks to me like you did you add the latest. > So is there the need to tell cherokee somewhere to use its statically > compiled-in plugins instead of looking for SOs and try to dlopen them? No. Whenever it tries to load a plug-in, it checks whether it's compiled-in. If not, it looks up for the plug-in as an alternative method to access the code. -- Octality http://www.octality.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
