Re: [concordance-devel] Next try for the big IR learning patch..
On Sunday 15 June 2008, Phil Dibowitz wrote: > I think you missed the point. It wasn't the 8.x that was the problem. It > was assigning a version number. Well, advocacy was never my business - but I'm getting it.. OK then, I'll keep my hands off any number that does not go into some computation, and let Stephen do his maintainer job. > This is fantastic! We have (as I'm sure you've seen), lots of Windows > users very stuck on the build process. As with everything else though, > I'd prefer to see this in the form of a patch - both for the sln/windows > build files and for the READMEs. Well, in the first place it's been a whole new file for me, that just happened to have the words 'INSTALL' and 'windows' in its name... And I must admit that, due to some problems with the different line terminators apparently, I so far failed to get a usable patch file for the windows build files that wasn't 100% old out and 100% new in. > Sounds great! I'm really excited about this effort. Unfortunately I > still haven't had a chance to review it at all. My apologies for that, > but spare time for me is still probably another 2 weeks out. I haven't > forgotten though - it's at the top of my TODO-when-I-have-2-moments-free > list. You're welcome - whenever you're ready, you're ready.. Andreas - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Next try for the big IR learning patch..
Andreas Schulz wrote: > First, my apology to Stephen - I didn't surely intend to interfere > with your release policy for congruity, but I just needed a new version, > and mindlessly decided that I would do well enough to it to deserve > a new major number. > Since I already told everyone around here to please ignore my > congruity8+ stuff, I shifted down to fractional 7.x versions, > so my final word (for the time) is now called congruity 7.4 > (see follow-up message). I think you missed the point. It wasn't the 8.x that was the problem. It was assigning a version number. If you call this 7.4, and he takes your patch and the 4 things in his local CVS and releases that as 7.4, now there's 2 7.4's out there. You are not responsible for releasing his code. The proper way to do this is to just send a patch which doesn't touch the version number - just like you would for libconcord or concordance. Stephen can then accept multiple patches and release when he feels the software is ready for a new release. Think of it this way - what if every patch to the linux kernel bumped it's version number up? We'd have linux 10billion. If, in some rare scenario, you *need* to change the version number (of which this case is not one of them), then the acceptable way to do that would be simply to define the version as 7.3+schulz1 or something like that. However, most people are likely to reject patches that change version numbers, so this should really be only for local testing, for example, to ensure code looking at minimum version numbers was functioning. > I have been busy this week (as long as I wasn't stuck at the TV > watching the Europe soccer championships..) switching back and > forth between WindowsXP and LINUX to get both concordance and > congruity sources finally working in both environments, adding > a few features and fixing some remaining bugs, removing warnings > by Visual C++ and trying to document the build process (and its > traps) for Windows. This is fantastic! We have (as I'm sure you've seen), lots of Windows users very stuck on the build process. As with everything else though, I'd prefer to see this in the form of a patch - both for the sln/windows build files and for the READMEs. (P.S. the Euro cup stuff here in Zurich is *insane*) > (tried .ZIP first, but apparently sourceforge doesn't like ZIP > attachments...) Sounds great! I'm really excited about this effort. Unfortunately I still haven't had a chance to review it at all. My apologies for that, but spare time for me is still probably another 2 weeks out. I haven't forgotten though - it's at the top of my TODO-when-I-have-2-moments-free list. -- Phil Dibowitz [EMAIL PROTECTED] Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming signature.asc Description: OpenPGP digital signature - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
[concordance-devel] Next try for the big IR learning patch..
First, my apology to Stephen - I didn't surely intend to interfere with your release policy for congruity, but I just needed a new version, and mindlessly decided that I would do well enough to it to deserve a new major number. Since I already told everyone around here to please ignore my congruity8+ stuff, I shifted down to fractional 7.x versions, so my final word (for the time) is now called congruity 7.4 (see follow-up message). I have been busy this week (as long as I wasn't stuck at the TV watching the Europe soccer championships..) switching back and forth between WindowsXP and LINUX to get both concordance and congruity sources finally working in both environments, adding a few features and fixing some remaining bugs, removing warnings by Visual C++ and trying to document the build process (and its traps) for Windows. Concordance IR learning is now full interactive with navigation back and forth trough the received command list and selection to learn codes from other remote or read Pronto hex codes. For congruity, I mostly had to fix the IR signal plot, which didn't work as well in Windows as in LINUX in the first version, and, in the course of the action, added the option to zoom in/out by left/right mouseclick. I am closing this first message attaching my experiences of building concordance on WindowsXP with Visual C++ 2005 Express, accompanied by a tgz archive of the win/concordance.sln and concordance/win/concordance.vcproj files to include libIRremotes into the concordance VC++ project. (tried .ZIP first, but apparently sourceforge doesn't like ZIP attachments...) Andreas Concordance build with MS Visual C++ 2005 Express Edition: -- Note: If want the latest and shiny, or just happen to have the DVD at hand (it has been published in some PC magazines recently), you may also get the 2008 Express edition, but AFAIR the download is larger, and the 2008 will convert the project files to its new format. With a CD/DVD, just go ahead installing - it should come ready with the SDK included. Otherwise, you will need: - MS Visual C++ 2005 Express Edition from Microsoft: http://www.microsoft.com/express/2005 You will first get an installer of ~2MB, which, when launched, will get the actual software of ~68MB. Adding Visual Studio plus service pack 1 when you start Microsoft update, which adds another 45MB. Note: You _MUST_ run the installer logged in as admin user, running it logged in as normal user with 'runas' will not work. - (parts of) the latest Windows SDK from: http://www.microsoft.com/downloads/details.aspx?FamilyId=E6E1C3DF-A74F-4207-8586-711EBE331CDC&displaylang=en This will give you another installer of merely ~400k. Run it (logged in as administrator) to install. It will initially offer you an impressive 1.2GB download - just may deselect everything, and then select just the 'Windows Headers and Libraries' section. This will strip the figure down to acceptable 27.3MB. It may complain about .NET development tools not selected - adding them would result in a total of 45.2MB (did that-who knows?). If you select the target directory for the install to $(VCInstallDir)\PlatformSDK, Visual C++ may be happy already (didn't try that). Otherwise, you have to: - include the SDK folders into Visual C++ 2005 Express Edition: - From the Visual C++ main menu, select Extra->Options - In the Options dialogue, select 'Projects and Project Folders ->VC++Folders' - Switch to 'Inlcude folders' and add the ...\include folder in the SDK installation folder. - Same for 'library folders' and the SDK ...\lib folder Now you should be set to compile concordance. CVS for Windows: If you want direct access to the concordance CVS from windows, you will need a Windows CVS client. There may be some around - I myself have installed Tortoise CVS (http://www.tortoisecvs.org/). In its extended settings panel (bottom line), you can select whether files from CVS shall be converted during checkout to DOS (CR/LF line terminator) or UNIX (LF line terminator) mode - you should select UNIX mode if you plan to apply patches that were created in a LINUX environment. Build concordance from CVS: --- - get concordance source from CVS (checkout or tarball, with concordance, libconcord, consnoop and win subdirectories plus some files) - double-click on win\concordance.dsw (VC++ 6 workspace file) to launch Visual Studio - You will get several messages that a current .vcproj file already exists - confirm with 'Yes' for each to load. - In the toolbar, select whether to build a 'Debug' or 'Release' version. - Select build->build project folder from the main menu - After probably a few warnings, build should be complete and end up with concordance.exe and libconcord.dll in the win/Debug resp. win/Release folder. - when you save the pr
