Of course nobody has to believe me, but probably the most convenient solution is to launch target using 'hbmk2 -hbrun my.hbp' (for standalone launch) or additional '-run' option (for build and launch operation).
This way there is no need to detect target executable name and everything is handled by hbmk2, where launching already works (or if there is any problem, we can fix it at one place). Brgds, Viktor On 2010 Apr 13, at 11:27, Barry Jackson wrote: > On 13/04/10 09:30, Przemysław Czerpak wrote: >> On Tue, 13 Apr 2010, Pritpal Bedi wrote: > >>> I need a functionality where new process executes normally at its own and >>> control is returned back to caller. How this can be achieved with >>> hb_processRun() ? >> >> You have to read my message once again. >> I gave you all necessary information. >> You have to use hb_processOpen(), i.e.: >> >> hProccess := hb_processOpen( cExecutable ) >> >> if hProccess != F_ERROR >> while ( nResult := hb_processValue( hProccess, .F. ) ) == -1 >> ? "waiting for process..." >> hb_idleSleep( 1 ) >> enddo >> ? "process terminated with result:", nResult >> endif >> >> best regards, >> Przemek > > I think I follow what Prital means:- > "...where new process executes normally on its own and control is returned > back to caller INSTANTLY without waiting for the process to complete." > > So that the built application will then run totally independently of hbide > and hbide may be used for other things or closed while the application is > running. > > Rgds, > Barry > > _______________________________________________ > 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
