Good evening Clinton and Sergey, My situation is probably one of those weird cases that doesn't arise for the vast majority. It could simply be a result of how I do things.
regards Bruce Rennie On 11/06/14 17:14, Jeffery, Clint ([email protected]) wrote: > > In principle, patchstr.exe will probably work the same under Windows > as it does under UNIX-based systems, and I endorse the idea of > including it in the Windows binary distribution in future builds. > Another possibility would be to bundle patchstr-style capabilities > into other tools as command-line options. > > > Anyhow, I am sure glad that patchstr has been useful to you, Bruce. > > > Cheers, > > Clint > > ------------------------------------------------------------------------ > *From:* Sergey Logichev <[email protected]> > *Sent:* Tuesday, June 10, 2014 9:10 PM > *To:* [email protected] > *Subject:* Re: [Unicon-group] Updating location of compiled binaries > [was previously : Question regarding search paths for iconx on Linux] > > Bruce, > > for Unicon problem with rigid link to iconx really persists. For > Windows it may be solved by putting all unicon and application > binaries in one directory. For Linux I managed to solve it by adding > location of unicon binaries to PATH variable. Your approach with > patchstr is really a workaround. But unfortunatelly under Windows make > doesn't create patchstr.exe. I think we shall humble ask Clint and > Jafar to include it. Or to try solve it as it done for Icon. > > Sergey > > 10.06.2014, 11:35, "Bruce & Breeanna Rennie" <[email protected]>: >> >> Good evening Sergey, >> >> Thanks for that. My problem has been that I have my production system in >> one location, including the IPL etc. I also have a second system which >> is my development system for changes I am looking at. This is in another >> location. I also have the latest SVN version as well, on which I run a >> variety of tests and changes. This is in a third location. >> >> Up to now, even with my PATH set accordingly, as well as IPATH and >> LPATH, when I do an update of the SVN version and before I do a full >> rebuild, I lose access to my production binaries as the internal path >> uses the SVN location. >> >> With the change I have made to my scripts, I don't have to concern >> myself with what is happening in the SVN version. Unicon now accesses >> the correct icont/iconx binaries for my production files. >> >> regards >> >> Bruce Rennie >> >> On 10/06/14 15:44, Sergey Logichev wrote: >> >> Bruce, >> >> Yes, with old version of icon and unicon too (however I am not sure >> for unicon) the problem was with correct path to iconx binary. >> For Icon v9.3.1 and 9.3.2 under Windows I usually put icont and >> iconx >> together. Then I compiled my program as: >> %path-to-icon%\icont -A myprogram.icn >> >> To run myprogram.exe I put %path-to-icon% to common PATH or copied >> icont/iconx to location of the program. Second way is working on >> 100%. >> >> But as it's turned on - it is because old icont had rigid path >> link to >> iconx in itself body. The same true for cygwin or linux. Then you >> build new executable with such icont the rigid link to iconx is >> inherited and cloned to executable. For Windows path problem maybe >> solved as I described, for unix patchstr was introduced. As I >> understood when you want to move iconx from original make >> location you >> need to patch icont only. Iconx doesn't point on itself. >> >> BTW starting with Icon 9.5 (as I remember) this "rigid chaining" of >> icont to iconx was cancelled. All path settings you can define >> through >> PATH variable. >> >> Best regards, >> Sergey Logichev >> >> 07.06.2014, 12:20, "Bruce & Breeanna Rennie" >> <[email protected] <mailto:[email protected]>>: >> >> To all, >> >> One problem that I have experienced was getting my system to >> use the >> correct binaries for icont and iconx. Previously, I have had >> some >> communications with Clinton on the [Unicon-ldif] list. I >> finally have >> found my solution and now understand a bit more of what >> Clinton was >> saying at the time. >> >> I am putting it my findings here for anyone else who >> regularly does >> rebuilds from source or wants to shift the location of the >> unicon/icon >> binaries. >> >> Courtesy of Ralph Griswold and his team, they have a lovely >> little >> program called patchstr. Up till now, I didn't understand >> its purpose. >> >> Using it on the icont and iconx binaries, I now have my >> system working >> as it should. >> >> I have placed two lines in my final rebuild shell script as >> follows >> >> patchstr icont "$HOME/unicon/bin" >> patchstr iconx "$HOME/unicon/bin" >> >> This leaves my normal working files now using the correct binary >> location. >> >> It just goes to show that even after many years of just using >> unicon/icon there is still more to learn. >> >> Thanks for your pointers Clinton and to those who >> contributed in the >> past with patchstr. >> >> regards >> >> Bruce Rennie >> >> >> >> ------------------------------------------------------------------------------ >> Learn Graph Databases - Download FREE O'Reilly Book >> "Graph Databases" is the definitive new guide to graph >> databases and >> their >> applications. Written by three acclaimed leaders in the field, >> this first edition is now available. Download your free book >> today! >> http://p.sf.net/sfu/NeoTech >> _______________________________________________ >> Unicon-group mailing list >> [email protected] >> <mailto:[email protected]> >> <mailto:[email protected] >> <mailto:[email protected]>> >> https://lists.sourceforge.net/lists/listinfo/unicon-group >> >> >> ------------------------------------------------------------------------------ >> HPCC Systems Open Source Big Data Platform from LexisNexis Risk >> Solutions >> Find What Matters Most in Your Big Data with HPCC Systems >> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. >> Leverages Graph Analysis for Fast Processing & Easy Data Exploration >> http://p.sf.net/sfu/hpccsystems >> >> >> _______________________________________________ >> Unicon-group mailing list >> [email protected] >> <mailto:[email protected]> >> https://lists.sourceforge.net/lists/listinfo/unicon-group >> >> ------------------------------------------------------------------------------ >> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions >> Find What Matters Most in Your Big Data with HPCC Systems >> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. >> Leverages Graph Analysis for Fast Processing & Easy Data Exploration >> http://p.sf.net/sfu/hpccsystems >> _______________________________________________ >> Unicon-group mailing list >> [email protected] >> <mailto:[email protected]> >> https://lists.sourceforge.net/lists/listinfo/unicon-group >> > > > ------------------------------------------------------------------------------ > HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions > Find What Matters Most in Your Big Data with HPCC Systems > Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. > Leverages Graph Analysis for Fast Processing & Easy Data Exploration > http://p.sf.net/sfu/hpccsystems > > > _______________________________________________ > Unicon-group mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/unicon-group ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ Unicon-group mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unicon-group
