On 17 Sep 2010, at 09:20, Nicola Pero wrote: > >> I don't see a conflict between the two. LanguageKit loads frameworks using >> NSBundle so that you can distribute a portable .app bundle with the source >> code in the bundle and a plist describing the frameworks that it needs. It >> loads the frameworks, JIT-compiles the code, and then runs the app. >> Apparently this doesn't work with the FHS layout, so Étoilé doesn't support >> systems that use the FHS layout. > > I'm not sure why this wouldn't work with the FHS layout if LanguageKit only > use the public NSBundle API. ;-)
It is using the public NSBundle API. > The public NSBundle API works fine with FHS. Usually things stop working > when you try to locate things manually > on disk instead of using the public API. The problem seems to be that frameworks are no longer found in the frameworks directory, and are no longer bundles, meaning that you have nothing meaningful to pass to NSBundle, so you can't load frameworks using NSBundle. If you can't load frameworks using NSBundle, then everything subsequently breaks because the JIT-compiled code doesn't find the classes that it requires. > If you have a pointer to the snippet of code that doesn't work, I can have a > look at some point and see if I can > suggest something. The code is in LanguageKit, but since I don't use the FHS layout, don't care about the FHS layout, and don't support the FHS layout, I can't tell you exactly which bit is failing - I just tell people not to use it when they complain stuff is broken. David _______________________________________________ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev