Menu
▾
▴
accessgrid-developer — Access Grid Developer Discussions
You can subscribe to this list here.
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(1) |
Sep
|
Oct
(3) |
Nov
|
Dec
|
|---|
|
From: Andrew D. <And...@ne...> - 2012-10-31 04:42:48
|
Hi Everyone, I've been working on getting vic and rat buildable under visual studio 2010. At this stage Rat is buildable but I need to rework how it loads the TCL scripts. My problem today is with building vic. In the file vic_tcl.h I keep getting the following error. 'return' : cannot convert from 'const char *' to 'char *' on line 77. It's a strange error as from what I can see several other methods within the same file use exactly the same form and do not cause errors. I've tried several different changes that just created different errors of a similar form. It seems that vs 2010 is a bit more strict when it comes to const types. Let me know what you guys think. Cheers Andrew |
|
From: Douglas K. <do...@uq...> - 2012-10-11 03:51:14
|
Hi Andrew, You need to embed the Tcl/Tk scripts (both runtime and RAT ones) into the RAT GUI executable. If you decided not to embed the Tcl/Tk runtime scripts into the executable, you would still need to tell the Tcl runtime where to find the scripts on the filesystem, I think by default it tries a few locations, but it is relative to where the rat-gui.exe is installed. UCL Tcl/Tk 8.0 was a modified version of Tcl/Tk that was suitable for use with Tcl2C to embed the Tcl/Tk scripts into C files (basically the scripts were just stored as C strings). Tcl2c isn't suitable for newer versions of Tcl/Tk, unless you want to heavy modify the Tcl/Tk runtime scripts as it will fail when an embedded script tries to explicitly source other scripts. Tcl 8.4 and later are Tcl 'virtual filesystem aware', so what I did with vic.exe and Tcl/Tk 8.5 was use a Zip VFS implementation, put all of the Tcl/Tk scripts (both runtime and vic ones) into a zip file and literally append the zip file to the end of vic.exe. You could have a look how I did vic.exe with VS2010. I did the VS 2010 solution from scratch as the migration from earlier VS projects had lots of crap which also interfered with the custom rules I used to build the zip file and append the zip file to the end of vic.exe. Have a look at the svn repository around the time the zvfs.c (Zip VFS implementation) was added to the vic mpeg4 svn repo : http://mediatools.cs.ucl.ac.uk/nets/mmedia/browser/vic/branches/mpeg4 ZIP 3.0 must not be used as it has a bug which prevents it from adjusting the ZIP offset of the zip file that gets appended to the executable. So use zip 2.x, 3.1 or later. Cheers, Doug > -----Original Message----- > From: Andrew Danson [mailto:And...@ne...] > Sent: Thursday, 11 October 2012 12:09 PM > To: acc...@li... > Subject: [AG-DEV] Building Rat on VS 2010 > > Hi Guys, > > I've noticed the list has been a bit quiet of late so I thought I might update > you on some stuff I've been doing. > > Rat and Vic are obviously important parts of the AG project so I have been > working on getting a working build of both these tools (using up to date > sources) on the windows platform using visual studio 2010. I also > downloaded newer sources for tcl and tk to use in the build process. > > So far I've made some good progress. I've managed to build a Rat binary by > making sure all the compiler paths and library paths were configured > correctly for my environment, and adding a library (iphlpapi.lib) into the > linker list so that ipv6 stuff is linked correctly on the windows 7 (vs 2010) > platform. The binary that I produced works in as far as it will transmit and > receive sound and appears in the list of participants on another instance of > Rat, but the UI portion of RAT crashes out and does not work. I was > wondering if anyone with some tcl knowledge could give me a clue as to why > this might be happening. It shouldn't be a tcl issue as rat compiles and works > under linux with a similarly new version of tcl and tk, but I don't see what else > it could be. > > > I've not yet made any progress much with compiling vic, it will be a lot > trickier. > > I've also spent some time learning about the SOAP interface and java > implementations of client stuff in the hope to learn a bit more about the > venue server and it's relationship with the client. I've been doing this as I've > found documentation a bit sparse, and this gave me a good idea of what kind > of messages are being passed between the two. Hopefully I can gain some > insight into the python code and how it works for the client. > > Cheers > Andrew |
|
From: Andrew D. <And...@ne...> - 2012-10-11 03:09:40
|
Hi Guys, I've noticed the list has been a bit quiet of late so I thought I might update you on some stuff I've been doing. Rat and Vic are obviously important parts of the AG project so I have been working on getting a working build of both these tools (using up to date sources) on the windows platform using visual studio 2010. I also downloaded newer sources for tcl and tk to use in the build process. So far I've made some good progress. I've managed to build a Rat binary by making sure all the compiler paths and library paths were configured correctly for my environment, and adding a library (iphlpapi.lib) into the linker list so that ipv6 stuff is linked correctly on the windows 7 (vs 2010) platform. The binary that I produced works in as far as it will transmit and receive sound and appears in the list of participants on another instance of Rat, but the UI portion of RAT crashes out and does not work. I was wondering if anyone with some tcl knowledge could give me a clue as to why this might be happening. It shouldn't be a tcl issue as rat compiles and works under linux with a similarly new version of tcl and tk, but I don't see what else it could be. I've not yet made any progress much with compiling vic, it will be a lot trickier. I've also spent some time learning about the SOAP interface and java implementations of client stuff in the hope to learn a bit more about the venue server and it's relationship with the client. I've been doing this as I've found documentation a bit sparse, and this gave me a good idea of what kind of messages are being passed between the two. Hopefully I can gain some insight into the python code and how it works for the client. Cheers Andrew |
|
From: Douglas K. <do...@uq...> - 2012-08-28 08:06:40
|
Hi, The AccessGrid subversion repository has been migrated to SourceForge and GitHub. The original head and tag SVN branches are on GitHub and the build and projects folders are on SourceForge. You can view the repos here: https://github.com/accessgrid/accessgrid http://sourceforge.net/p/accessgrid/svn/ People were keen to move to Git, but due to the svn:externals and non-standard SVN build and projects folders, that wasn't possible to do completely on SourceForge. Fortunately GitHub provides a SVN interface, so I was able to point the svn:external properties in the build folder on SourceForge to the AccessGrid GitHub repo. More details can be found in the README file here: http://sourceforge.net/p/accessgrid/svn/7/tree/trunk/build/ Subversion repositories previous hosted by ANL for Bajjer (Python Jabber module used by AGTk) and IF -Media (from ANU's Internet Futures lab and includes VPCScreen amongst others) can now be found by clicking on the Bajjer and IF-Media buttons on the following page : http://sourceforge.net/projects/accessgrid/ Cheers, Doug |
|
From: Christoph W. <c.w...@uq...> - 2012-06-13 23:41:08
|
Welcome to the accessgrid-developer email list at Sourceforge. This is the new community driven email list for Access Grid developer discussions. It replaces the previous ag-dev list run from ANL. Have fun! |
|
From: Christoph W. <c.w...@uq...> - 2012-06-13 22:36:50
|
Welcome to the accessgrid-developer email list at Sourceforge. This is the new community driven email list for Access Grid developer discussions. It replaces the previous ag-dev list run from ANL. Have fun! |
