From: Andreas K. <and...@ac...> - 2008-07-10 15:57:52
|
> > Even so, we still have task /3/ to consider. While most of the actual > > work on it will undoubtedly be dependent on the completion of /2/ and > > its sub-tasks we can still make reasonable guesses about them, and > > some we should be able to work on even with /2/ stalled. So, what is > > needed for the proper integration: > > > > /4/ Write all necessary code to call the functions > > provided by /2/ from Tcl, handle the returned values. > > Do you mean that I should add to the Tcl core (for example to > tclLoadDl.c) some code which uses the function provided by /2/ like > elf_dlopen, etc.? Yes. We have to implement ELF specific variants of the two functions TclpLoadMemoryGetBuffer() and TclpLoadMemory(), and modify TclpFindSymbol(). > > /6/ Create a subdirectory rtld/doc in our project > > repository and add a text file which details the > > results of /5/. > I wrote some text, but it is quite general and I am not sure if it is > what you thought about. In particular, I did not wrote much about > functions in unix/tclLoadDyld.c. I focused about how it looks from > generic/tclIOUtil.c. Ok. Will review after updating my repository ... Hm, I see the doc directory, however it seems to be empty. > > Going back to the sub-tasks needed to complete /3/: > > > > /7/ Extend Tcl's configuration system to activate loading > > from memory for Linux. > > > > Subtask: > > > > /8/ Determine how the configuration system (= the > > file configure.in) activates the support for > > OS X. > > I just changed configure.in so that it defines TCL_LOAD_FROM_MEMORY if > the operating system is Linux. Ok. Will review. > > /9/ Extend Tcl's build system to compile and link all new > > C files we will get from /4/. > > > > Subtask: > > > > /10/ Determine how Tcl's build system (= the file > > Makefile.in) compiles existing C files. > > Because there is quite a lot of files in rtld, I am thinking of adding > a new directory to (like elf-dyloader) to tcl/unix. Then we have to > options: > - we can add to elf-dyloader a Makefile which makes a library; we will > change Makefile.in so that this library will be linked with the rest > of the tcl code > - we can make all needed changes in Makefile.in I do not believe that we (= the maintainers of the Tcl core) have experience with sub Makefiles and sub-libraries. As such I would prefer if everything we do is in the unix/Makefile.in. I was thinking about a subdirectory of unix as well. I had a different name in my mind for it, however the exact name is mostly like the color of the bikeshed [1], so I refrain from mentioning it. [1] http://en.wikipedia.org/wiki/Color_of_the_bikeshed > > /12/ Document the relationships between our major pieces of > > code, in text and/or drawing, put the result into the > > trunk/rtld/doc directory. > > I am not sure if I fully understand what exactly I am supposed to do here. Hm. I was hoping to get a drawing which shows the different pieces as boxes, possibly with important function names inside, and various arrows between them showing us, roughly, which pieces calls on what others. Even more highlevel than the call trees actually. -- Andreas Kupries <andreask@ActiveState.com> Developer @ http://www.ActiveState.com Tel: +1 778-786-1122 |