On 13 July 2012 21:20, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
On 13 July 2012 19:24, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
<snip> > Yippie! > > It works :-). I patched it up to work with the more modern /sys interface > and it now works very very well. > > Tim, what should we do now? It needs a conversion to CMake probably first, > but then what? can I check it into a new repository?
What is wrong with the Automake version? If you want to port it to CMake that's up to you, but first I would have someone with GIT access check it in to a new module.
Can you give me permissions to just this repository?
What is the exact name of the applet? Would hdaps-monitor be appropriate?
It is currently called khdapsmonitor. I think the name is fine but hdaps-monitor works as well.
As a side note, I have not built this with Trinity R14, but on 3.5.13, some appropriate linking might be necessary.
Can you try to get it building on R14 before we officially add it to GIT?
I have created an empty repository for this application, and granted you write access to it. Use this command to pull it: git clone http://<username>@scm.trinitydesktop.org/scm/git/hdaps-monitor
When you check in the new application, make sure all of the following files are removed prior to commit if they exist: configure Makefile.in Makefile admin/ cmake/ all object files and binaries
When you have the initial version in GIT, let me know and I will add the admin/ and cmake/ submodules.
Tim
I will port it to cmake because automake is ugly.
I do not have a Trinity R14 system up and running. Darrell or David, could you test and verify it works with R14 (just that it compiles, to run it successfully you need a thinkpad)
Calvin