on 9/11/07 9:49 AM, Ruslan Zasukhin at [EMAIL PROTECTED] wrote: > On 11/9/07 4:12 PM, "Chris Little" <[EMAIL PROTECTED]> wrote: > >> REALbasic 2007r4 has two new debugging features designed to support plugin >> developers. The development tools used to write plugins need a way to >> interface with REALbasic to be able to run plugins under their source-level >> debuggers. Generally, they do this by building a shared library into a >> certain location, and then launching an executable (of the user's choice) >> which is responsible for loading the shared library. In previous versions >> of REALbasic, there was no simple way to debug plugins because the RB >> compiler would embed the plugin code into its output instead of using the >> original plugin file on disk. > > So what ?? > > I was able quite easy debug source of Valentina for RB always. > as using CodeWarrior, so using xcode, so using Visual on Windows. > > Yes RB product MyApp.app which has COPY of plugin. > > I just write small script in the XCODE Project's Target, which replace this > plugin in .app folder on HARD LINK to original debug plugin in the BUILD > folder. And it works like a charm. > > > But of course its great that RB is improved in this area.
But you couldn't do this on Windows. That is the big difference with this change. You can now debug plugins on Mac and Windows. > >> REALbasic 2007r4 now allows you to specify >> "debugging" plugins, so that RB's compiler links its executables against the >> original file instead of copying the plugin code into the output app. > > >> This feature set is designed to cover two use cases: debugging plugin code, >> and debugging plugin code while debugging REALbasic code. > > Good, up to now debugging BOTH C++ sources of plugin and RB code was not > possible. > Agreed. Chris _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
