>> Please Jean-Brieuc give it a try and give me some feedback about it. >> >> Thanks, >> Gastón. >> > Thank you for sharing your work! > > I successfully generated the shared library and could run your demo tcl file. > > I have some comments which could be integrated to the readme file in the zip > archive. > It would ease installation for future users. > - TCL v8.6 is required as object oriented TCL (OO TCL) is necessary, TCL 8.5 > is > not sufficient. Executing the libwrapper main.tcl script with tclsh8.6 is then > recommended. Yes, TclOO is only required to run the automated scripts, the extension can be compiled to Tcl 8.5.
> -A small modification to the source/Tclurjtag.c file is necessary for linux > compilation. Replace the header name 'Tcl.h' to 'tcl.h' This also work for windows, so I.ve added it to the scripts. > -In the readme document, replace "change to 'sources' directory" by "change to > 'source' directory" Ok. > > I also had some warning during the compilation: > Tclurjtag.c: In function ‘urj_set_dr_Cmd’: > Tclurjtag.c:118:2: warning: pointer targets in passing argument 3 of > ‘tclStubsPtr->tcl_GetLongFromObj’ # # differ in signedness [-Wpointer-sign] > Tclurjtag.c:118:2: note: expected ‘long int *’ but argument is of type ‘long > unsigned int *’ Strange, I don't see the same in Cygwin.. I should check this. > mv: cannot stat `pkgIndex.tcl': No such file or directory Yes, 'pkgIndex.tcl' is generated by the scripts (just to set the Tclurjtag version), so if you run "make.sh" twice the second will raise this error. I will change the scripts to send this file to the extension directory and no to 'source'. > > Here is my make file, which should fit linux users: > > #!/bin/sh > > # Path to the tcl headers (tcl.h, ...) > export TCLINC="/usr/local/include" > # Path to the libtcl8.6.so file > export TCLLIB="/usr/local/lib" > # Path to the libftd2xx.so file > export FTD2XX="/usr/local/lib" > export URJTAG_BASE="~/SVN_urjtag/trunk/urjtag" > > # Input and output files name > export TARGET="Tclurjtag" > # Destination file of the generated library and pkgIndex.tcl > export TARGET_PATH="../Tclurjtag" > export INCLUDES="-I$URJTAG_BASE -I$URJTAG_BASE/include -I$FTD2XX -I$TCLINC" > > export LIBS="-L$URJTAG_BASE/src/.libs/ -lurjtag -L$FTD2XX -lftd2xx -L$TCLLIB > -ltclstub8.6" > > gcc -Wall -O2 -shared -o $TARGET.so $TARGET.c $INCLUDES -DUSE_TCL_STUBS $LIBS > > mv $TARGET.so $TARGET_PATH > mv pkgIndex.tcl $TARGET_PATH Good! > > > Finally, is there any documentation about the new tcl functions available? Not really. The API is 'altmost' the same that the API of liburjtag, so documenting this one should be enough. But also in the first release I put along with the extension another package 'Jtag' that encapsulate some of the most useful features. This package can be extended and documented, maybe using the same interface that use the Python UrJtag binding. > If not, the demo is sufficient to understand how to use this Tcl binding > library! > > So, thank you very much for your help Gaston, > > Regards, > > J-B > > PS: If needed, I can send you via PM the Tclurjtag.so file in order to join it > to the zip archive... > > Yes of course! Is for Linux ix86 or amd64? Thanks a lot! Gastón. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ UrJTAG-development mailing list UrJTAG-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/urjtag-development
