Re: [Harbour] Introducing myself
Well, we will have to play ball, WP has many rules and it serves the whole thing pretty well, so either we should talk with the guy and/or streamline the article to adhere with the requirements. Reliable 3rd party references were missing, so I've added some hard statistics (now also an ohloh page). We may also use citations from forums (clipper.borda.ru, hmgforum.com, pctoledo.com.br, comp.lang.clipper), and our own mailing list. F.e. there was great debate between Przemek and Xbase++ owner Steffen F. Pirsig: http://www.mail-archive.com/harbour@harbour-project.org/msg10164.html (and follow-up replies/corrections to this article) Brgds, Viktor On 2010 Apr 10, at 01:51, Antonio Maniero wrote: It's a shame but this edit will be deleted soon by Yworo wikipedia's user. he is a experient user and know all wp laws. I was finding for mailing list statistics ;-) Thanks []'s Maniero 2010/4/9 Viktor Szakáts harbour...@syenar.hu i propose add c:\harbour\doc\xhp-dif.txt to wikipedia page I've added it a few hours ago. Brgds, Viktor ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
[Harbour] SF.net SVN: harbour-project:[14306] trunk/harbour
Revision: 14306 http://harbour-project.svn.sourceforge.net/harbour-project/?rev=14306view=rev Author: vszakats Date: 2010-04-10 08:18:05 + (Sat, 10 Apr 2010) Log Message: --- 2010-04-10 10:13 UTC+0200 Viktor Szakats (harbour.01 syenar.hu) * external/zlib/zlib.dif * external/zlib/zconf.h ! Tweak to make it build with BCC (when this specific constant is defined, f.e. by libharu). * external/pcre/Makefile ! Tweak to make 8.02 work with BCC. ; NOTE: BCC is seemingly not tested/used by any important external projects. If it goes like this, I will stop doing these updates and leave them to real BCC users. It's going against the flow. * config/postinst.prg * /V2 - -V2 to make *nix shells happy. Modified Paths: -- trunk/harbour/ChangeLog trunk/harbour/config/postinst.prg trunk/harbour/external/pcre/Makefile trunk/harbour/external/zlib/zconf.h trunk/harbour/external/zlib/zlib.dif This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
[Harbour] Re: Ubuntu issue building hbpcre lib
Hola Teo: ¿cómo puedo obtener wxHarbour con el SVN? [ENG by Google] Hi Teo: WxHarbour how I can get the SVN? TIA BestRegards GVS Teo Fonrouge escribió: Hello Marco, On Apr 8, 2010, at 7:23 AM, marco bra wrote: Many thanks to Premzek and Viktor for the clear answer. Surely i will send some note to the developer of wxHarbour BTW i was solving this compiling samples issue with this statement: make HBLIBSTYPE=shared The samples coming into the wxHarbour directory structure have singles GNUmakefile, one for directory and these files seems to be auto generated by http://www.bakefile.org http://www.bakefile.org/ as far i can read in all the GNUmakefile files header, i suppose Bakefile tool don't generate hbmk2 make statement (i don't know that tool). The hbmk2 utility is working ok in the wxHarbour library. To build the library: 1. Change to your current wxHarbour directory: $ cd wxHarbour 2. Build the lib using hbmk2: $ hbmk2 wxharbour.hbp If all goes ok, then you can try to build a sample: 1. Change to any sample dir: $ cd samples/dbf_ctrls1 2. Build the sample using hbmk2 with the wxharbour.hbc file: $ hbmk2 ../../wxharbour.hbc dbf_ctrls1.prg 3. If all goes ok, then run the sample: $ ./dbf_ctrls1 Please test after SVN: Revision: 572 http://wxharbour.svn.sourceforge.net/wxharbour/?rev=572view=rev http://wxharbour.svn.sourceforge.net/wxharbour/?rev=572view=rev Author: tfonrouge Date: 2010-04-08 23:19:11 + (Thu, 08 Apr 2010) best regards, Teo ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
Re: [Harbour] Re: Ubuntu issue building hbpcre lib
Hi Guillermo, On Apr 10, 2010, at 7:44 AM, Guillermo Varona Silupú wrote: Hola Teo: ¿cómo puedo obtener wxHarbour con el SVN? [ENG by Google] Hi Teo: WxHarbour how I can get the SVN? ENGLISH First at all, you need a SVN client. On Linux based OS you may install the subversion package using the package manager. On Windows here is a very good command line based SVN client: http://tortoisesvn.net/downloads Once that you have your SVN client installed, you just need to do a checkout: 1. [optional] Create a SVN dir on your computer and change to it. 2. Execute the following command (is a single line): svn co https://wxharbour.svn.sourceforge.net/svnroot/wxharbour/trunk/wxHarbour wxHarbour 3. Change to the wxharbour directory and just build the library the samples. Once that you have your SVN based wxharbour directory, to update to last revision, you just have to execute on it: svn update /ENGLISH SPANISH Primero que nada, necesitas un cliente SVN En Linux puedes instalar el paquete subversion utilizando el manejador de paquetes. En Windows aqui hay muy buen cliente SVN que se puede utilizar desde la linea de comandos: http://tortoisesvn.net/downloads Una vez que tienes el cliente SVN instalado, solo necesitas efectuar un checkout: 1. [opcional] Crea un directorio SVN y cambiate a el. 2. Executa el siguiente comando (es una sola linea): svn co https://wxharbour.svn.sourceforge.net/svnroot/wxharbour/trunk/wxHarbour wxHarbour 3. Cambiate al directorio wxharbour y construye la libreria y ejemplos. Una vez que tienes tu directorio SVN de wxharbour, para actualizar a la ultima version, solo tienes que executar: svn update /SPANISH [snip] best regards, Teo ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
Re: [Harbour] What wrong with this example ....Harbour + Qt + hbxbp ...
I can't test your app Appevent.ch is missing Bruno 2010/4/10 Shum wcshu...@hotmail.com Hi All, I make the attached example: ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
[Harbour] Re: What wrong with this example ....Harbour + Qt + hbxbp ...
Hi Bruno, Please remakr the line of //include appevent.ch or remove it and please pay attention to the tst.hbp file The line -ld:\10\hprg\tgui.dll The path (d:\10\hprg\ should be the location of your disk and path of tgui.dll ) Shum http://n2.nabble.com/file/n4882289/PTST.ZIP PTST.ZIP -- View this message in context: http://n2.nabble.com/What-wrong-with-this-example-Harbour-Qt-hbxbp-tp4880826p4882289.html Sent from the harbour-devel mailing list archive at Nabble.com. ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
[Harbour] Close to our Polish colleagues
I am deeply sorry to hear the news. I am close to our Polish colleagues and I hope the best for their beautiful country. Lorenzo Fiorini ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
[Harbour] Re: Close to our Polish colleagues
Lorenzo Fiorini wrote: I am deeply sorry to hear the news. I am close to our Polish colleagues and I hope the best for their beautiful country. An unwanted tragedy. I am shocked. My sympathies. - enjoy hbIDEing... Pritpal Bedi http://hbide.vouch.info/ -- View this message in context: http://n2.nabble.com/Close-to-our-Polish-colleagues-tp4882472p4882554.html Sent from the harbour-devel mailing list archive at Nabble.com. ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
Re: [Harbour] Re: Close to our Polish colleagues
Yes 2010/4/10 Pritpal Bedi bediprit...@hotmail.com: Lorenzo Fiorini wrote: I am deeply sorry to hear the news. I am close to our Polish colleagues and I hope the best for their beautiful country. -- Massimo Belgrano ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
[Harbour] Re: What wrong with this example ....Harbour + Qt + hbxbp ...
Hi All, Another version of the testing 1.) Modify tst.prg and tgui.prg for remark appevent.ch 2.) tst1.hbp and btst1.bat is added for showing workable sample 3.) for the old version will showing the (dll and exe) not working error please pay attention to tst.hbp as follow: The path (d:\10\hprg\ should be the location of your disk and path of tgui.dll ) Shum http://n2.nabble.com/file/n4882603/PTST.ZIP PTST.ZIP -- View this message in context: http://n2.nabble.com/What-wrong-with-this-example-Harbour-Qt-hbxbp-tp4880826p4882603.html Sent from the harbour-devel mailing list archive at Nabble.com. ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
Re: [Harbour] Close to our Polish colleagues
I am deeply sorry to hear the news. I am close to our Polish colleagues and I hope the best for their beautiful country. Same from me. It was very sad to hear that today morning, I'm wishing the best luck and recovery from this event. Brgds, Viktor ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
Re: [Harbour] Introducing myself
Some rules I've learned: Mailing list can't be used as reliable source :-( Non-english sources too WP has so many rules, some of them are ambiguous and contradictory. It's party to an wikipedia's attorney shows and make trouble where everything walks ok. You missed my discussion about newsgroup citation. He deleted the citation. He shows me the rule. Ok. But I challenge him to deleted same source about Linux History where Linus call for help on kernel development. He runs away. The Harbour article have so many problems he not stated... The biggest problem is he pick bureaucratic problems, not content problems. If all WP rules going to be apllied the majority articles will be vanished from WP. Most of Citation needed was putted for me. The problem is get reliable sources with so many rules. I am trying to make the article conform to WP standards, have sure about that. Yworo wants delete Harbour article in favor of xBase article. If Harbour article is superfluous, thousands and thousands articles are superfluous too, but this is not a argument, there is a rule denying this type of argument. Nobody fix the same problem in famous articles because there are too many forces to fight against. In summary, who knows the WP process, knows WP is a place to people expresses power. The majority WP rules are contrary to original intent of WP when Jimbo creates it. BTW, this post has the best value for me because I knew about the MT debate :-) I think we need create an index to valuable posts like msg10164. []'s Maniero 2010/4/10 Viktor Szakáts harbour...@syenar.hu Well, we will have to play ball, WP has many rules and it serves the whole thing pretty well, so either we should talk with the guy and/or streamline the article to adhere with the requirements. Reliable 3rd party references were missing, so I've added some hard statistics (now also an ohloh page). We may also use citations from forums (clipper.borda.ru, hmgforum.com, pctoledo.com.br, comp.lang.clipper), and our own mailing list. F.e. there was great debate between Przemek and Xbase++ owner Steffen F. Pirsig: http://www.mail-archive.com/harbour@harbour-project.org/msg10164.html (and follow-up replies/corrections to this article) Brgds, Viktor ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
Re: [Harbour] Introducing myself
Hi Antonio, Some rules I've learned: Mailing list can't be used as reliable source :-( We should try. We have nothing to hide and we're not lying, so I believe all we need to do is put convincing sources behind our statements. F.e. the guy deleted the word fast. Now, we have lots and lots of speed comparisons with Clipper, Xbase++ and xhb, so the back it up, we can just link to such a result posted on the mailing list. And see what happens. In general I agree with the notion of backing up claims from as many (possibly external) sources as possible. Harbour is small community, so finding external source is not easy, so we should use what we have. F.e. you can quote speed comparison posted by xhb developers on xhb mailing list. F.e. this thread: http://permalink.gmane.org/gmane.comp.lang.xharbour.devel/3012 Non-english sources too It should be okay if linked through Google Translate. WP has so many rules, some of them are ambiguous and contradictory. It's party to an wikipedia's attorney shows and make trouble where everything walks ok. You missed my discussion about newsgroup citation. He deleted the citation. He shows me the rule. Ok. But I challenge him to deleted same source about Linux History where Linus call for help on kernel development. He runs away. I've also jumped to lots of links pointing to mail archives. Which means we should try and if the pointed article seems reasonable, I think it will be ok. We should see anyway. The Harbour article have so many problems he not stated... The biggest problem is he pick bureaucratic problems, not content problems. Of course, because he probably uses some sort of automated tool to do rough verification on articles which received heavy changes in short time period. Such tool will look for keywords and hard rules which are just not noticed or enforced when coming in small steps. At least so I imagine. Yworo wants delete Harbour article in favor of xBase article. If Harbour article is superfluous, thousands and thousands articles are superfluous too, but this is not a argument, there is a rule denying this type of argument. Nobody fix the same problem in famous articles because there are too many forces to fight against. So he should also delete Clipper, xHarbour, Xbase++ and FlagShip compiler articles as well. This is plain nonsense, just ignore it, or point him these articles. A general xBase article is good idea, but the details are always put on distinct pages. In summary, who knows the WP process, knows WP is a place to people expresses power. The majority WP rules are contrary to original intent of WP when Jimbo creates it. BTW, this post has the best value for me because I knew about the MT debate :-) I think we need create an index to valuable posts like msg10164. Yes, absolutely. Brgds, Viktor ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
[Harbour] SF.net SVN: harbour-project:[14307] trunk/harbour
Revision: 14307 http://harbour-project.svn.sourceforge.net/harbour-project/?rev=14307view=rev Author: vszakats Date: 2010-04-10 17:53:53 + (Sat, 10 Apr 2010) Log Message: --- 2010-04-10 19:46 UTC+0200 Viktor Szakats (harbour.01 syenar.hu) * contrib/hbqt/hbqt.ch - Deleted unused HBQT_DEBUG() macro. Pls use HB_TRACE( HB_TR_*, ... ) to make it obvious where trace calls are made. (Same should be done in HBXBP) * contrib/hbqt/THbQtUI.prg * Replaced static hbq_dbg() function with HB_TRACE( HB_TR_ALWAYS, ... ) calls. This makes sure that the trace call is dynamically toggled. * contrib/hbide/hbide.prg - Deleted __HBIDE_DEBUG__ forced define, which in turn forcefully enabled user-environment options HB_TR_DEBUG and HB_TR_WINOUT. I beg: Please set these on your local environment. That's the whole point of these settings. Unconditionally setting them in app code is not good idea. Go to Control Panel / System / Local environment and just add them there (if you need them) and case is closed. This should also fix excessive log output when simply using HBIDE. ! Fixed missing space between revision and filename in title bar. % Cleaned retrieving Harbour revision for title bar. ; Most above changes target to make HBQT/HBIDE tracing behave just like other parts of Harbour (without losing functionality). Pls don't revert them. Modified Paths: -- trunk/harbour/ChangeLog trunk/harbour/contrib/hbide/hbide.prg trunk/harbour/contrib/hbqt/THbQtUI.prg trunk/harbour/contrib/hbqt/hbqt.ch This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
[Harbour] SF.net SVN: harbour-project:[14308] trunk/harbour
Revision: 14308 http://harbour-project.svn.sourceforge.net/harbour-project/?rev=14308view=rev Author: vszakats Date: 2010-04-10 17:58:50 + (Sat, 10 Apr 2010) Log Message: --- 2010-04-10 19:58 UTC+0200 Viktor Szakats (harbour.01 syenar.hu) * contrib/hbide/ideobject.prg * contrib/hbide/idefunctions.prg * contrib/hbide/idefindreplace.prg * contrib/hbide/idesources.prg * contrib/hbide/idethemes.prg * contrib/hbide/ideeditor.prg * contrib/hbide/hbide.prg * contrib/hbide/idemisc.prg * contrib/hbide/idesaveload.prg * contrib/hbide/ideshortcuts.prg * contrib/hbide/ideprojmanager.prg ! Replaced static hbide_dbg() function call with HB_TRACE( HB_TR_ALWAYS, ... ) calls. This should also fix excessive permanently enabled debug messages when using HBIDE. Pls keep it that way. BTW, probably HB_TR_ALWAYS should be changed to some lower priority. Modified Paths: -- trunk/harbour/ChangeLog trunk/harbour/contrib/hbide/hbide.prg trunk/harbour/contrib/hbide/ideeditor.prg trunk/harbour/contrib/hbide/idefindreplace.prg trunk/harbour/contrib/hbide/idefunctions.prg trunk/harbour/contrib/hbide/idemisc.prg trunk/harbour/contrib/hbide/ideobject.prg trunk/harbour/contrib/hbide/ideprojmanager.prg trunk/harbour/contrib/hbide/idesaveload.prg trunk/harbour/contrib/hbide/ideshortcuts.prg trunk/harbour/contrib/hbide/idesources.prg trunk/harbour/contrib/hbide/idethemes.prg This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
Re: [Harbour] Re: Ubuntu issue building hbpcre lib
Teo, on an fresh installation of Ubuntu 10.04 32 bits, harbour Rev. 14306 and wxHarbour Rev. 574 from svn : After installing this deb packages: sudo apt-get install libwxbase2.8-dev libwxgtk2.8-dev wx-common so i have a wx-config --version - 2.8.10 Compiling with: hbmk2 wxharbour.hbp compile fine, then doing: cd samples/dbf_ctrls1 hbmk2 ../../wxharbour.hbc dbf_ctrls1.prg ./dbf_ctrls1 Work fine... thank you Best regards, Marco ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
[Harbour] SF.net SVN: harbour-project:[14309] trunk/harbour
Revision: 14309 http://harbour-project.svn.sourceforge.net/harbour-project/?rev=14309view=rev Author: vouchcac Date: 2010-04-10 19:09:02 + (Sat, 10 Apr 2010) Log Message: --- 2010-04-10 12:04 UTC-0800 Pritpal Bedi (prit...@vouchcac.com) * contrib/hbxbp/xbpdialog.prg + Added :sysMenu instance variable picked from Shum's example. Modified Paths: -- trunk/harbour/ChangeLog trunk/harbour/contrib/hbxbp/xbpdialog.prg This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
[Harbour] Re: What wrong with this example ....Harbour + Qt + hbxbp ...
Thanks Pritpal Bedi , If oDlg:destroy() is called just before RETURN statement, it does not GPF. It solve the exit GPF... 1. You are linking with -shared flag, so you need harbourmt21.dll alongside exe 2. If tst.exe is built with tgui.dll then it GPF's Yes GPF still there even copy the harbourmt-21.dll into the tst.exe dir ... Hope other can help . Shum -- View this message in context: http://n2.nabble.com/What-wrong-with-this-example-Harbour-Qt-hbxbp-tp4880826p4883172.html Sent from the harbour-devel mailing list archive at Nabble.com. ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
Re: [Harbour] Introducing myself
We should try. We have nothing to hide and we're not lying, so I believe all we need to do is put convincing sources behind our statements. I totally agree. F.e. the guy deleted the word fast. Now, we have lots and lots of speed comparisons with Clipper, Xbase++ and xhb, so the back it up, we can just link to such a result posted on the mailing list. And see what happens. I agree although I think he is right. Fast is a very subjective concept. It's possible give proofs about that, of course. It should be okay if linked through Google Translate. In general, it's not okay. And yes, WP has a lot of this citations. So he should also delete Clipper, xHarbour, Xbase++ and FlagShip compiler articles as well. This is plain nonsense, just ignore it, or point him these articles. A general xBase article is good idea, but the details are always put on distinct pages. He stalking Harbour article for now. My idea is improving xBase article and left implementations details for compilers and interpreters. But this require time. One thing to each time. I can not get Harbour's article polished yet. I am having problems with Dmoz too, but still trying. At least in that case, Harbour is there already. I will try to improve the criteria about TIOBE is indexing xBase languages. Anyway I gave the kick off on english. My wish is sell harbour to portuguese speakers. I can do a better job in my natural language. BTW, this post has the best value for me because I knew about the MT debate :-) I think we need create an index to valuable posts like msg10164. Yes, absolutely. It's in my TODO list ;-) but I can't do it alone. BTW, I thinks it's off-topic but I am curious about past issues on Clipper's and Harbour's history. I will start a new thread if nobody objects about this a few OT. []'s Maniero ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
Re: [Harbour] Introducing myself
On Sat, Apr 10, 2010 at 6:52 PM, Antonio Maniero mani...@klip.net wrote: Some rules I've learned: ... []'s Maniero Excuse my jump in and feel free to ignore everything. For me WP should be only a place where to say that Harbour exist and what it is while the details and comparisons should be elsewhere. I understand that expression like fast, modern or unlike Java need to be proved and that a sentence like Most softwares originally writen to run on Xbase++, Flagship, FoxPro, xHarbour and others dialects can be compiled with Harbor with some adaptation. can be critical. I've used FoxPro in the past and I can say that some adaption is not the term I'd use for a conversion :) Instead you could summarize the introduction leaving only the facts like: ... Harbour is an open source computer programming language. The compiler, the runtime and the support libraries are written in Ansi C and Harbour itself so they can be built on every operating system that has a compatible C compiler. Harbour is known to work under Microsoft Windows, Linux, Mac OS X, BSD, Windows CE, OS/2 Ecomstation, Haiku/BeOS. The open source Harbour license[1] is similar to the GNU General Public License, with an exception supporting commercial applications, so commercial applications can be produced with Harbour and distributed. ... Concepts like multiple graphic terminals or replaceable database driver are difficult to explain in few sentences and can be even misleading so I would remove them. In general I think you could present Harbour as a language by itself instead of a Clipper clone. The vast majority of developers don't know what Clipper is so references to it are almost useless. Then you could add some code examples trying to make the code as clean as possible starting with: function main() outstd( Hello World ) return I would avoid: - mention macro - things like ? or QOut - terms like procedure or routine - show both begin sequence and try catch syntax - using DO x - show DO CASE best regards, Lorenzo think ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
[Harbour] hbIDE - Invoked from Console ( development ) vs Desktop Icon
Hello Viktor hbIDE run from console window which is used to compile/link/run under development. NOTE: this I am doing since very begining I started on hbQT+. hbMK2 executes properly and builds the targets ok. But since yesterday night I Build and Run feature of hbIDE produces this log. Strange part is that if I run same hbIDE.exe from desktop icon and execute Build and Run it works perfectly. Probably this may lead us to detect why on *nixes the same operation fails. Below are logs from hbIDE invoked from the development console and from desktop. [ FROM CONSOLE ] Project [ TST ]Launch [ Yes ]Rebuild [ Yes ]Started [ 12:22:58 ] C:\DOCUME~1\Pritpal\LOCALS~1\Temp\pj2i3p.bat : Exists /C C:\DOCUME~1\Pritpal\LOCALS~1\Temp\pj2i3p.bat hbmk2 C:\harbour\contrib\hbide\projects\tst.hbp -q -trace -info -lang=en -rebuild Starting in: harbour\contrib\hbide : C:\harbour\contrib\hbide\projects\ C:\harbour\contrib\hbide\projectsset PATH=c:\mingw\bin;c:\qt\2009.03\qt\bin; C:\harbour\contrib\hbide\projectsset PATH=c:\harbour;c:\harbour\harbour\mingw\bin;c:\mingw\bin;c:\qt\2009.03\qt\bin; C:\harbour\contrib\hbide\projectsset HB_WITH_QT=c:\qt\2009.03\qt 'hbmk2' is not recognized as an internal or external command, operable program or batch file. Exit Code [ 1 ]Exit Status [ 0 ]Finished at [ 12:22:58 ]Done in [ 0.20 Secs ] Sorry, cannot launch project because of errors... 2nd Build and Launch Project [ TST ]Launch [ Yes ]Rebuild [ No ]Started [ 12:29:26 ] C:\DOCUME~1\Pritpal\LOCALS~1\Temp\lg4tiu.bat : Exists /C C:\DOCUME~1\Pritpal\LOCALS~1\Temp\lg4tiu.bat hbmk2 C:\harbour\contrib\hbide\projects\tst.hbp -q -trace -info -lang=en Starting in: harbour\contrib\hbide : C:\harbour\contrib\hbide\projects\ C:\harbour\contrib\hbide\projectsset PATH=c:\mingw\bin;c:\qt\2009.03\qt\bin; C:\harbour\contrib\hbide\projectsset PATH=c:\harbour;c:\harbour\harbour\mingw\bin;c:\mingw\bin;c:\qt\2009.03\qt\bin; C:\harbour\contrib\hbide\projectsset HB_WITH_QT=c:\qt\2009.03\qt 'hbmk2' is not recognized as an internal or external command, operable program or batch file. Exit Code [ 1 ]Exit Status [ 0 ]Finished at [ 12:29:26 ]Done in [ 0.19 Secs ] Sorry, cannot launch project because of errors... Two builds were just to check if .bat is unique to both of them. [ hbIDE run from desktop icon ] Project [ TST ]Launch [ Yes ]Rebuild [ No ]Started [ 12:39:02 ] C:\DOCUME~1\Pritpal\LOCALS~1\Temp\rli88v.bat : Exists /C C:\DOCUME~1\Pritpal\LOCALS~1\Temp\rli88v.bat hbmk2 C:\harbour\contrib\hbide\projects\tst.hbp -q -trace -info -lang=en Starting in: harbour\contrib\hbide : C:\harbour\contrib\hbide\projects\ C:\harbour\contrib\hbide\projectsset PATH=C:\mingw\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Intel\Wireless\Bin;C:\Program Files\Microsoft Office\OFFICE11\Business Contact Manager\IM;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft Office\OFFICE11\Business Contact Manager\;C:\Program Files\Common Files\InterSystems\Cache;C:\WINDOWS\system32\nls;C:\WINDOWS\system32\nls\ENGLISH C:\harbour\contrib\hbide\projectsset PATH=C:\harbour_dev;C:\harbour_dev\harbour\mingw\bin;C:\mingw\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Intel\Wireless\Bin;C:\Program Files\Microsoft Office\OFFICE11\Business Contact Manager\IM;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft Office\OFFICE11\Business Contact Manager\;C:\Program Files\Common Files\InterSystems\Cache;C:\WINDOWS\system32\nls;C:\WINDOWS\system32\nls\ENGLISH C:\harbour\contrib\hbide\projectsset
[Harbour] Re: hbIDE - Invoked from Console ( development ) vs Desktop Icon
Pritpal Bedi wrote: Hello Viktor hbIDE run from console window which is used to compile/link/run under development. NOTE: this I am doing since very begining I started on hbQT+. hbMK2 executes properly and builds the targets ok. But since yesterday night I Build and Run feature of hbIDE produces this log. Strange part is that if I run same hbIDE.exe from desktop icon and execute Build and Run it works perfectly. Probably this may lead us to detect why on *nixes the same operation fails. Wait, I think I have messed up something. - enjoy hbIDEing... Pritpal Bedi http://hbide.vouch.info/ -- View this message in context: http://n2.nabble.com/hbIDE-Invoked-from-Console-development-vs-Desktop-Icon-tp4883224p4883231.html Sent from the harbour-devel mailing list archive at Nabble.com. ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
Re: [Harbour] Introducing myself
Good thoughts. Brgds, Viktor On 2010 Apr 10, at 21:40, Lorenzo Fiorini wrote: On Sat, Apr 10, 2010 at 6:52 PM, Antonio Maniero mani...@klip.net wrote: Some rules I've learned: ... []'s Maniero Excuse my jump in and feel free to ignore everything. For me WP should be only a place where to say that Harbour exist and what it is while the details and comparisons should be elsewhere. I understand that expression like fast, modern or unlike Java need to be proved and that a sentence like Most softwares originally writen to run on Xbase++, Flagship, FoxPro, xHarbour and others dialects can be compiled with Harbor with some adaptation. can be critical. I've used FoxPro in the past and I can say that some adaption is not the term I'd use for a conversion :) Instead you could summarize the introduction leaving only the facts like: ... Harbour is an open source computer programming language. The compiler, the runtime and the support libraries are written in Ansi C and Harbour itself so they can be built on every operating system that has a compatible C compiler. Harbour is known to work under Microsoft Windows, Linux, Mac OS X, BSD, Windows CE, OS/2 Ecomstation, Haiku/BeOS. The open source Harbour license[1] is similar to the GNU General Public License, with an exception supporting commercial applications, so commercial applications can be produced with Harbour and distributed. ... Concepts like multiple graphic terminals or replaceable database driver are difficult to explain in few sentences and can be even misleading so I would remove them. In general I think you could present Harbour as a language by itself instead of a Clipper clone. The vast majority of developers don't know what Clipper is so references to it are almost useless. Then you could add some code examples trying to make the code as clean as possible starting with: function main() outstd( Hello World ) return I would avoid: - mention macro - things like ? or QOut - terms like procedure or routine - show both begin sequence and try catch syntax - using DO x - show DO CASE best regards, Lorenzo think ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
[Harbour] Re: Ubuntu issue building hbpcre lib
Gracias Teo, ya pude bajar los funtes del SVN, sin embargo, aun no he podido generar la LIB y por ende los ejemplos. Solamente he bajado e instalado esto: http://ufpr.dl.sourceforge.net/project/wxwindows/wxMSW/2.8.10/wxMSW-2.8.10-Setup.exe luego compilo con esto: D:\wxHarbour\hrbmingw\bin\hbmk2 wxharbour.hbp y obtengo esta lista de warnings y errores: . . . ed in this scope src/common/sysdefs.cpp:152: error: `wxEVT_SIZE' was not declared in this scope src/common/sysdefs.cpp:153: error: `wxEVT_MOVE' was not declared in this scope src/common/sysdefs.cpp:154: error: `wxEVT_CLOSE_WINDOW' was not declared in this scope src/common/sysdefs.cpp:155: error: `wxEVT_END_SESSION' was not declared in this scope src/common/sysdefs.cpp:156: error: `wxEVT_QUERY_END_SESSION' was not declared in this scope src/common/sysdefs.cpp:157: error: `wxEVT_ACTIVATE_APP' was not declared in this scope src/common/sysdefs.cpp:159: error: `wxEVT_ACTIVATE' was not declared in this sco pe src/common/sysdefs.cpp:160: error: `wxEVT_CREATE' was not declared in this scope src/common/sysdefs.cpp:161: error: `wxEVT_DESTROY' was not declared in this scop e src/common/sysdefs.cpp:162: error: `wxEVT_SHOW' was not declared in this scope src/common/sysdefs.cpp:163: error: `wxEVT_ICONIZE' was not declared in this scop e src/common/sysdefs.cpp:164: error: `wxEVT_MAXIMIZE' was not declared in this sco pe src/common/sysdefs.cpp:165: error: `wxEVT_MOUSE_CAPTURE_CHANGED' was not declare d in this scope src/common/sysdefs.cpp:166: error: `wxEVT_MOUSE_CAPTURE_LOST' was not declared i n this scope src/common/sysdefs.cpp:167: error: `wxEVT_PAINT' was not declared in this scope src/common/sysdefs.cpp:168: error: `wxEVT_ERASE_BACKGROUND' was not declared in this scope src/common/sysdefs.cpp:169: error: `wxEVT_NC_PAINT' was not declared in this sco pe src/common/sysdefs.cpp:171: error: `wxEVT_MENU_OPEN' was not declared in this sc ope src/common/sysdefs.cpp:172: error: `wxEVT_MENU_CLOSE' was not declared in this s cope src/common/sysdefs.cpp:173: error: `wxEVT_MENU_HIGHLIGHT' was not declared in th is scope src/common/sysdefs.cpp:174: error: `wxEVT_CONTEXT_MENU' was not declared in this scope src/common/sysdefs.cpp:175: error: `wxEVT_SYS_COLOUR_CHANGED' was not declared i n this scope src/common/sysdefs.cpp:176: error: `wxEVT_DISPLAY_CHANGED' was not declared in t his scope src/common/sysdefs.cpp:178: error: `wxEVT_QUERY_NEW_PALETTE' was not declared in this scope src/common/sysdefs.cpp:179: error: `wxEVT_PALETTE_CHANGED' was not declared in t his scope src/common/sysdefs.cpp:180: error: `wxEVT_JOY_BUTTON_DOWN' was not declared in t his scope src/common/sysdefs.cpp:181: error: `wxEVT_JOY_BUTTON_UP' was not declared in thi s scope src/common/sysdefs.cpp:182: error: `wxEVT_JOY_MOVE' was not declared in this sco pe src/common/sysdefs.cpp:183: error: `wxEVT_JOY_ZMOVE' was not declared in this sc ope src/common/sysdefs.cpp:184: error: `wxEVT_DROP_FILES' was not declared in this s cope src/common/sysdefs.cpp:188: error: `wxEVT_INIT_DIALOG' was not declared in this scope src/common/sysdefs.cpp:190: error: `wxEVT_IDLE' was not declared in this scope src/common/sysdefs.cpp:191: error: `wxEVT_UPDATE_UI' was not declared in this sc ope src/common/sysdefs.cpp:192: error: `wxEVT_SIZING' was not declared in this scope src/common/sysdefs.cpp:193: error: `wxEVT_MOVING' was not declared in this scope src/common/sysdefs.cpp:194: error: `wxEVT_HIBERNATE' was not declared in this sc ope src/common/sysdefs.cpp:198: error: `wxEVT_COMMAND_TEXT_COPY' was not declared in this scope src/common/sysdefs.cpp:199: error: `wxEVT_COMMAND_TEXT_CUT' was not declared in this scope src/common/sysdefs.cpp:200: error: `wxEVT_COMMAND_TEXT_PASTE' was not declared i n this scope src/common/sysdefs.cpp:204: error: `wxEVT_COMMAND_LEFT_CLICK' was not declared i n this scope src/common/sysdefs.cpp:205: error: `wxEVT_COMMAND_LEFT_DCLICK' was not declared in this scope src/common/sysdefs.cpp:206: error: `wxEVT_COMMAND_RIGHT_CLICK' was not declared in this scope src/common/sysdefs.cpp:207: error: `wxEVT_COMMAND_RIGHT_DCLICK' was not declared in this scope src/common/sysdefs.cpp:208: error: `wxEVT_COMMAND_SET_FOCUS' was not declared in this scope src/common/sysdefs.cpp:209: error: `wxEVT_COMMAND_KILL_FOCUS' was not declared i n this scope src/common/sysdefs.cpp:210: error: `wxEVT_COMMAND_ENTER' was not declared in thi s scope src/common/sysdefs.cpp:213: error: `wxEVT_COMMAND_NOTEBOOK_PAGE_CHANGED' was not declared in this scope src/common/sysdefs.cpp:214: error: `wxEVT_COMMAND_NOTEBOOK_PAGE_CHANGING' was no t declared in this scope src/common/sysdefs.cpp:216: error: `wxEVT_HELP' was not declared in this scope src/common/sysdefs.cpp:217: error: `wxEVT_DETAILED_HELP' was not declared in thi s scope src/common/sysdefs.cpp:220: error: `wxEVT_DATE_CHANGED' was not declared in this scope
[Harbour] Re: hbIDE - Invoked from Console ( development ) vs Desktop Icon
Pritpal Bedi wrote: Wait, I think I have messed up something. And certainly I did. Sorry for the noise and ignore it. - enjoy hbIDEing... Pritpal Bedi http://hbide.vouch.info/ -- View this message in context: http://n2.nabble.com/hbIDE-Invoked-from-Console-development-vs-Desktop-Icon-tp4883224p4883260.html Sent from the harbour-devel mailing list archive at Nabble.com. ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
Re: [Harbour] Introducing myself
For me WP should be only a place where to say that Harbour exist and what it is while the details and comparisons should be elsewhere. I disagree although the article need be cleaned up. I bring a lot things from Clipper and xHarbour article to be polished. It's a matter of balance and you can contribute on article It is not mine. Look at another programming languages articles about details. I understand that expression like fast, modern or unlike Java need to be proved and that a sentence like Most softwares originally writen to run on Xbase++, Flagship, FoxPro, xHarbour and others dialects can be compiled with Harbor with some adaptation. can be critical. I've used FoxPro in the past and I can say that some adaption is not the term I'd use for a conversion :) I agree, It is not my text. Feel free to change it. You can discuss about that on WP too. Some WP editors don't read this mailing list. Instead you could summarize the introduction leaving only the facts like: ... Harbour is an open source computer programming language. The compiler, the runtime and the support libraries are written in Ansi C and Harbour itself so they can be built on every operating system that has a compatible C compiler. Harbour is known to work under Microsoft Windows, Linux, Mac OS X, BSD, Windows CE, OS/2 Ecomstation, Haiku/BeOS. The open source Harbour license[1] is similar to the GNU General Public License, with an exception supporting commercial applications, so commercial applications can be produced with Harbour and distributed. ... Good. Concepts like multiple graphic terminals or replaceable database driver are difficult to explain in few sentences and can be even misleading so I would remove them. In general I think you could present Harbour as a language by itself instead of a Clipper clone. The vast majority of developers don't know what Clipper is so references to it are almost useless. It's not my text but I think this is need be better written. We can't hide this information too. Then you could add some code examples trying to make the code as clean as possible starting with: function main() outstd( Hello World ) return I would avoid: - mention macro - things like ? or QOut - terms like procedure or routine - show both begin sequence and try catch syntax - using DO x - show DO CASE In general, it's my intent reduce this. It's first attempt to improve the article. Look xHarbour article to understand why it's ugly. Remember I am the first to criticize my edits ;-) And look to old Harbour's article. My main goal is done: shaking the list about the subject. Anyway, feel free to change the article. Personally I code in C style. A typical Clipper programmer don't recognize my code as xBase program. Unfortunately we still need sell Harbour to Clipper programmer. I repeat, this view is going against my personal preference but I think it is necessary comparing old (dBase) style to new (Harbour) style. Thanks to your suggestions. []'s Maniero ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
Re: [Harbour] Re: Ubuntu issue building hbpcre lib
Hello Guillermo, On Apr 10, 2010, at 2:50 PM, Guillermo Varona Silupú wrote: Gracias Teo, ya pude bajar los funtes del SVN, sin embargo, aun no he podido generar la LIB y por ende los ejemplos. Solamente he bajado e instalado esto: http://ufpr.dl.sourceforge.net/project/wxwindows/wxMSW/2.8.10/wxMSW-2.8.10-Setup.exe luego compilo con esto: D:\wxHarbour\hrbmingw\bin\hbmk2 wxharbour.hbp y obtengo esta lista de warnings y errores: . . . Seems that you aren't yet builded the wxWidgets library, you just downloaded it. In order to build wxWidgets you need to execute the following: Using MinGW, In directory: C:\wxWidgets-2.8.10/build/msw: mingw32-make.exe -f makefile.gcc INCLUDE=C:\MinGW/include LIB=C:\MinGW/lib USE_XRC=1 BUILD=release UNICODE=1 WXUNIV=0 MONOLITHIC=0 USE_EXCEPTIONS=1 USE_ODBC=0 USE_OPENGL=0 USE_MEDIA=0 USE_RICHTEXT=1 USE_HTML=1 USE_XRC=1 USE_AUI=1 USE_GUI=1 RUNTIME_LIBS=dynamic SHARED=0 all Using MSVC, In directory: C:\wxWidgets-2.8.10/build/msw: nmake /nologo -f makefile.vc INCLUDE=C:\Program Files\Microsoft SDKs\Windows\v6.0A\include;C:\Program Files\Microsoft Visual Studio 9.0\vc\include LIB=C:\Program Files\Microsoft SDKs\Windows\v6.0A\lib;C:\Program Files\Microsoft Visual Studio 9.0\vc\lib USE_XRC=1 BUILD=release UNICODE=1 WXUNIV=0 MONOLITHIC=0 USE_EXCEPTIONS=1 USE_ODBC=0 USE_OPENGL=0 USE_MEDIA=0 USE_RICHTEXT=1 USE_HTML=1 USE_XRC=1 USE_AUI=1 USE_GUI=1 RUNTIME_LIBS=dynamic SHARED=0 all Using BCC 55, In directory: C:\wxWidgets-2.8.10/build/msw: make -f makefile.bcc INCLUDE=C:\Borland\BCC55\include LIB=C:\Borland\BCC55\lib;C:\Borland\BCC55\lib\psdk USE_XRC=1 BUILD=release UNICODE=1 WXUNIV=0 MONOLITHIC=0 USE_EXCEPTIONS=1 USE_ODBC=0 USE_OPENGL=0 USE_MEDIA=0 USE_RICHTEXT=1 USE_HTML=1 USE_XRC=1 USE_AUI=1 USE_GUI=1 RUNTIME_LIBS=dynamic SHARED=0 all [snip] best regards, Teo ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
Re: [Harbour] Close to our Polish colleagues
I have seen now news from online newspapers after read messages in the list. I'm deeply sorry too. Best wishes to Polish friends. Best regards, Francesco Viktor Szakáts ha scritto: I am deeply sorry to hear the news. I am close to our Polish colleagues and I hope the best for their beautiful country. Same from me. It was very sad to hear that today morning, I'm wishing the best luck and recovery from this event. Brgds, Viktor ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
[Harbour] SF.net SVN: harbour-project:[14310] trunk/harbour
Revision: 14310 http://harbour-project.svn.sourceforge.net/harbour-project/?rev=14310view=rev Author: vouchcac Date: 2010-04-10 23:21:56 + (Sat, 10 Apr 2010) Log Message: --- 2010-04-10 16:11 UTC-0800 Pritpal Bedi (prit...@vouchcac.com) * contrib/hbide/idedocks.prg * contrib/hbide/ideenviron.prg * contrib/hbide/idefindreplace.prg * contrib/hbide/idemisc.prg * contrib/hbide/ideprojmanager.prg * contrib/hbide/ideshortcuts.prg * contrib/hbide/idesources.prg * contrib/hbxbp/hbpprocess.prg ! Fixed error when double-click on build output was causing GPF if no editor tab is in focus, i.e., Welcome tabs are visible. - Removed some loggings. % Reworked how build commands are called. Now only one batch file is sent to the process engine to fire and rest is contained into that batch file. It probably may solve *nix issue where a .sh is not executed or any other command with long list of params. Modified Paths: -- trunk/harbour/ChangeLog trunk/harbour/contrib/hbide/idedocks.prg trunk/harbour/contrib/hbide/ideenviron.prg trunk/harbour/contrib/hbide/idefindreplace.prg trunk/harbour/contrib/hbide/idemisc.prg trunk/harbour/contrib/hbide/ideprojmanager.prg trunk/harbour/contrib/hbide/ideshortcuts.prg trunk/harbour/contrib/hbide/idesources.prg trunk/harbour/contrib/hbxbp/hbpprocess.prg This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
[Harbour] My first study on hbqt code...
Let's start with
qtgui/QPushButton.cpp
HB_FUNC( QT_QPUSHBUTTON_SETAUTODEFAULT )
{
hbqt_par_QPushButton( 1 )-setAutoDefault( hb_parl( 2 ) );
}
Since
#define hbqt_par_QPushButton( n ) ( ( QPushButton
* ) hbqt_gcpointer( n ) )
this line:
hbqt_par_QPushButton( 1 )-setAutoDefault( hb_parl( 2 ) );
becomes:
( ( QPushButton * ) hbqt_gcpointer( 1 ) )-setAutoDefault( hb_parl( 2 ) );
In hbqt_destruct.cpp there is hbqt_gcpointer(). Its job is to return
the pointer to the object.
For every Qt object hbqt actually stores a struct, and in pq member it
stores a guarded pointer that is binded to the object at creation
time. A guarded pointer is a special pointer that is guaranteed to
became NULL if the binded object is deleted. QPointer may only be
created for objects descending from QObject.
Guarded pointers are important since (from what I understood from my
readings) there are many different possibilities for object
destruction, for example using MT, where a thread can delete an object
while another is updating it...
In the objects destructor ( the hbqt_gcRelease_* functions ) pq value
is checked against NULL... But in hbqt_gcpointer it is not... because
in hbqt_gcpointer we just have a generic QGC_POINTER and not the
specific QGC_POINTER_QPushButton so pq is not available...
See:
typedef struct
{
void * ph;
bool bNew;
QT_G_FUNC_PTR func;
QPointer QPushButton pq;
} QGC_POINTER_QPushButton;
typedef struct
{
void * ph;
bool bNew;
QT_G_FUNC_PTR func;
} QGC_POINTER;
My idea is then to add a Qpointer placeholder in QGC_POINTER but it
would need some more changes, infact it seems ok for objects in
directory qtgui (they descend from QObject) but not for objects in
qtcore that doesn't inherit from QObject.
So there are 2 possibilities to verify:
1) in hbqt.h change the #define hbqt_par_QPushButton( n ) ( (
QPushButton * ) hbqt_gcpointerFromQObject( n ) ) for object in qtgui
and then copy hbqt_gcpointer to hbqt_gcpointerFromQObject adding pq
checking (the some for *FromObj) but then how to handle Q_release ?
2) using bNew not as a bool but as a bitmask with values
1=CREATED_BY_NEW 2=HAS_PQ 4=INVALID 8=DELETE_IN_PROGRESS (to
trap/debug strange interactions between c++ delete and harbour GC)
giving us a clear picture of what is happening and also a lot more
status bit to use
Using 2) it may be just a matter of adding the status bit at object
creation and checking the 1-ness of bit 2 before testing pq and some
other trivial changes...
Francesco
___
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
Re: [Harbour] Re: Ubuntu issue building hbpcre lib
Hello Guillermo, On Apr 10, 2010, at 3:55 PM, Teo Fonrouge wrote: Hello Guillermo, On Apr 10, 2010, at 2:50 PM, Guillermo Varona Silupú wrote: Gracias Teo, ya pude bajar los funtes del SVN, sin embargo, aun no he podido generar la LIB y por ende los ejemplos. Solamente he bajado e instalado esto: http://ufpr.dl.sourceforge.net/project/wxwindows/wxMSW/2.8.10/wxMSW-2.8.10-Setup.exe luego compilo con esto: D:\wxHarbour\hrbmingw\bin\hbmk2 wxharbour.hbp y obtengo esta lista de warnings y errores: . . . Seems that you aren't yet builded the wxWidgets library, you just downloaded it. In order to build wxWidgets you need to execute the following: Using MinGW, In directory: C:\wxWidgets-2.8.10/build/msw: mingw32-make.exe -f makefile.gcc INCLUDE=C:\MinGW/include LIB=C:\MinGW/lib USE_XRC=1 BUILD=release UNICODE=1 WXUNIV=0 MONOLITHIC=0 USE_EXCEPTIONS=1 USE_ODBC=0 USE_OPENGL=0 USE_MEDIA=0 USE_RICHTEXT=1 USE_HTML=1 USE_XRC=1 USE_AUI=1 USE_GUI=1 RUNTIME_LIBS=dynamic SHARED=0 all Using MSVC, In directory: C:\wxWidgets-2.8.10/build/msw: nmake /nologo -f makefile.vc INCLUDE=C:\Program Files\Microsoft SDKs\Windows\v6.0A\include;C:\Program Files\Microsoft Visual Studio 9.0\vc\include LIB=C:\Program Files\Microsoft SDKs\Windows\v6.0A\lib;C:\Program Files\Microsoft Visual Studio 9.0\vc\lib USE_XRC=1 BUILD=release UNICODE=1 WXUNIV=0 MONOLITHIC=0 USE_EXCEPTIONS=1 USE_ODBC=0 USE_OPENGL=0 USE_MEDIA=0 USE_RICHTEXT=1 USE_HTML=1 USE_XRC=1 USE_AUI=1 USE_GUI=1 RUNTIME_LIBS=dynamic SHARED=0 all Using BCC 55, In directory: C:\wxWidgets-2.8.10/build/msw: make -f makefile.bcc INCLUDE=C:\Borland\BCC55\include LIB=C:\Borland\BCC55\lib;C:\Borland\BCC55\lib\psdk USE_XRC=1 BUILD=release UNICODE=1 WXUNIV=0 MONOLITHIC=0 USE_EXCEPTIONS=1 USE_ODBC=0 USE_OPENGL=0 USE_MEDIA=0 USE_RICHTEXT=1 USE_HTML=1 USE_XRC=1 USE_AUI=1 USE_GUI=1 RUNTIME_LIBS=dynamic SHARED=0 all After checking the wxharbour.hb? files, I see that they are building/linking against the NON-UNICODE version of the wxWidgets library. So please change in the above commands the clause: - UNICODE=1 to UNICODE=0 - This in order to use the current wxharbour.hb? files in SVN. Important: Also you need to set the HB_WITH_WX var to something like set HB_WITH_WX=C:\wxWidgets-2.8.10\include After following the above steps, the library samples are builded ok by using the hbmk2 utility with the wxharbour.hb? scripts. best regards, Teo ___ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
[Harbour] hbmk2: expanding env vars on windows
Hello,
On an *.hbc script, there is the following line:
-i{mingw}${HB_WITH_WX}\..\lib\gcc_lib\msw
If I set the HB_WITH_WX var with:
set HB_WITH_WX=C:\wxWidgets-2.8.10
then it's incorrectly expanded to:
-LC:/lib/gcc_lib
If I set the HB_WITH_WX var with:
set HB_WITH_WX=C:\wxWidgets-2.8.10\include
then it's correctly expanded to:
-LC:/wxWidgets-2.8.10/lib/gcc_lib
It's correctly behavior ? If so, why ?
best regards,
Teo
___
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
[Harbour] SF.net SVN: harbour-project:[14311] trunk/harbour
Revision: 14311 http://harbour-project.svn.sourceforge.net/harbour-project/?rev=14311view=rev Author: vouchcac Date: 2010-04-11 02:45:23 + (Sun, 11 Apr 2010) Log Message: --- 2010-04-10 19:35 UTC-0800 Pritpal Bedi (prit...@vouchcac.com) * contrib/hbqt/qtcore/*.cpp * contrib/hbqt/qtgui/*.cpp * contrib/hbqt/qtnetwork/*.cpp ! Regenerated sources with changes in logging format and addition. Modified Paths: -- trunk/harbour/ChangeLog trunk/harbour/contrib/hbqt/generator/hbqtgen.prg trunk/harbour/contrib/hbqt/qtcore/HBDbfModel.cpp trunk/harbour/contrib/hbqt/qtcore/HBEvents.cpp trunk/harbour/contrib/hbqt/qtcore/HBSlots.cpp trunk/harbour/contrib/hbqt/qtcore/QAbstractItemModel.cpp trunk/harbour/contrib/hbqt/qtcore/QAbstractListModel.cpp trunk/harbour/contrib/hbqt/qtcore/QAbstractTableModel.cpp trunk/harbour/contrib/hbqt/qtcore/QBitArray.cpp trunk/harbour/contrib/hbqt/qtcore/QBuffer.cpp trunk/harbour/contrib/hbqt/qtcore/QByteArray.cpp trunk/harbour/contrib/hbqt/qtcore/QChar.cpp trunk/harbour/contrib/hbqt/qtcore/QCoreApplication.cpp trunk/harbour/contrib/hbqt/qtcore/QDataStream.cpp trunk/harbour/contrib/hbqt/qtcore/QDate.cpp trunk/harbour/contrib/hbqt/qtcore/QDateTime.cpp trunk/harbour/contrib/hbqt/qtcore/QDir.cpp trunk/harbour/contrib/hbqt/qtcore/QEvent.cpp trunk/harbour/contrib/hbqt/qtcore/QEventLoop.cpp trunk/harbour/contrib/hbqt/qtcore/QFile.cpp trunk/harbour/contrib/hbqt/qtcore/QFileInfo.cpp trunk/harbour/contrib/hbqt/qtcore/QIODevice.cpp trunk/harbour/contrib/hbqt/qtcore/QLatin1Char.cpp trunk/harbour/contrib/hbqt/qtcore/QLatin1String.cpp trunk/harbour/contrib/hbqt/qtcore/QLine.cpp trunk/harbour/contrib/hbqt/qtcore/QLineF.cpp trunk/harbour/contrib/hbqt/qtcore/QList.cpp trunk/harbour/contrib/hbqt/qtcore/QLocale.cpp trunk/harbour/contrib/hbqt/qtcore/QMimeData.cpp trunk/harbour/contrib/hbqt/qtcore/QModelIndex.cpp trunk/harbour/contrib/hbqt/qtcore/QObject.cpp trunk/harbour/contrib/hbqt/qtcore/QPoint.cpp trunk/harbour/contrib/hbqt/qtcore/QPointF.cpp trunk/harbour/contrib/hbqt/qtcore/QProcess.cpp trunk/harbour/contrib/hbqt/qtcore/QRect.cpp trunk/harbour/contrib/hbqt/qtcore/QRectF.cpp trunk/harbour/contrib/hbqt/qtcore/QRegExp.cpp trunk/harbour/contrib/hbqt/qtcore/QResource.cpp trunk/harbour/contrib/hbqt/qtcore/QSettings.cpp trunk/harbour/contrib/hbqt/qtcore/QSignalMapper.cpp trunk/harbour/contrib/hbqt/qtcore/QSize.cpp trunk/harbour/contrib/hbqt/qtcore/QSizeF.cpp trunk/harbour/contrib/hbqt/qtcore/QStringList.cpp trunk/harbour/contrib/hbqt/qtcore/QTextBoundaryFinder.cpp trunk/harbour/contrib/hbqt/qtcore/QTextCodec.cpp trunk/harbour/contrib/hbqt/qtcore/QTextDecoder.cpp trunk/harbour/contrib/hbqt/qtcore/QTextEncoder.cpp trunk/harbour/contrib/hbqt/qtcore/QTextStream.cpp trunk/harbour/contrib/hbqt/qtcore/QThread.cpp trunk/harbour/contrib/hbqt/qtcore/QTime.cpp trunk/harbour/contrib/hbqt/qtcore/QTimer.cpp trunk/harbour/contrib/hbqt/qtcore/QTranslator.cpp trunk/harbour/contrib/hbqt/qtcore/QUiLoader.cpp trunk/harbour/contrib/hbqt/qtcore/QUrl.cpp trunk/harbour/contrib/hbqt/qtcore/QVariant.cpp trunk/harbour/contrib/hbqt/qtcore/TQChar.prg trunk/harbour/contrib/hbqt/qtgui/HBQMainWindow.cpp trunk/harbour/contrib/hbqt/qtgui/HBQPlainTextEdit.cpp trunk/harbour/contrib/hbqt/qtgui/HBQSyntaxHighlighter.cpp trunk/harbour/contrib/hbqt/qtgui/HBQTableView.cpp trunk/harbour/contrib/hbqt/qtgui/HBQTextBlockUserData.cpp trunk/harbour/contrib/hbqt/qtgui/QAbstractButton.cpp trunk/harbour/contrib/hbqt/qtgui/QAbstractItemDelegate.cpp trunk/harbour/contrib/hbqt/qtgui/QAbstractItemView.cpp trunk/harbour/contrib/hbqt/qtgui/QAbstractPrintDialog.cpp trunk/harbour/contrib/hbqt/qtgui/QAbstractProxyModel.cpp trunk/harbour/contrib/hbqt/qtgui/QAbstractScrollArea.cpp trunk/harbour/contrib/hbqt/qtgui/QAbstractSlider.cpp trunk/harbour/contrib/hbqt/qtgui/QAbstractSpinBox.cpp trunk/harbour/contrib/hbqt/qtgui/QAbstractTextDocumentLayout.cpp trunk/harbour/contrib/hbqt/qtgui/QAction.cpp trunk/harbour/contrib/hbqt/qtgui/QActionGroup.cpp trunk/harbour/contrib/hbqt/qtgui/QApplication.cpp trunk/harbour/contrib/hbqt/qtgui/QBitmap.cpp trunk/harbour/contrib/hbqt/qtgui/QBoxLayout.cpp trunk/harbour/contrib/hbqt/qtgui/QBrush.cpp trunk/harbour/contrib/hbqt/qtgui/QButtonGroup.cpp trunk/harbour/contrib/hbqt/qtgui/QCalendarWidget.cpp trunk/harbour/contrib/hbqt/qtgui/QCheckBox.cpp trunk/harbour/contrib/hbqt/qtgui/QClipboard.cpp trunk/harbour/contrib/hbqt/qtgui/QColor.cpp trunk/harbour/contrib/hbqt/qtgui/QColorDialog.cpp trunk/harbour/contrib/hbqt/qtgui/QComboBox.cpp trunk/harbour/contrib/hbqt/qtgui/QCommandLinkButton.cpp trunk/harbour/contrib/hbqt/qtgui/QCommonStyle.cpp
Re: [Harbour] hbmk2: expanding env vars on windows
On Apr 10, 2010, at 8:35 PM, Teo Fonrouge wrote:
Hello,
On an *.hbc script, there is the following line:
-i{mingw}${HB_WITH_WX}\..\lib\gcc_lib\msw
Ok, now I got a little more knowledge on hbmk2
and I see where the problem is:
\..\
[snip]
Sorry for the noise.
best regards,
Teo
___
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
