From: Robert D. <rcd...@gm...> - 2009-05-30 19:34:56
|
So I found out that adobe::find_resource() is being used to try to find glossary.xstr. However, it only uses the root_path() for searching, which isn't very flexible at all. How about making this function check a few more places, in particular the working directory. Also, it would be a nice feature to be able to specify a list of resource directories at the command line for the begin app and have those be used for searching for resources, amongst other obvious paths. Doing this will prevent me from having to copy files around via CMake to ensure that resources can be found. I can make these changes myself, if you guys think it would be a good idea. I'm leaning more towards the command-line parameter approach for specifying resource directories. Another comment: The root_path() is basically a singleton, and not thread safe at all. It would be ideal to make resource "hints" a concept, possibly create a new class called ResourceRepository, which can be given directory hints (where to find resources) and can be used to obtain resources. On Fri, May 29, 2009 at 7:56 PM, Robert Dailey <rcd...@gm...> wrote: > Hello, > So I've got the Begin app compiling and linking under CMake, however it > cannot find resources during the loading process. I pointed the working > directory in Visual Studio to the begin/resources directory, but this does > not seem to help. I tried referencing the bjam scripts as well, but since I > am not familiar with bjam I had trouble finding anything helpful. > > Can anyone give me some pointers? It is trying to find *glossary.xstr*. > |