Xojo Developer Conference
25/27th April 2018 in Denver.
MBS Xojo Conference
6/7th September 2018 in Munich, Germany.

AppleScript on CodeWarrior (Real Studio Plugins Mailinglist archive)

Back to the thread list
Previous thread: Re: Debugging plugins in Xcode ... 2.1
Next thread: Image Resizing in Win32...


macosx and unix paths   -   GOLD
  AppleScript on CodeWarrior   -   Björn Eiríksson <b
   Re: AppleScript on CodeWarrior   -   Björn Eiríksson <b
   Re: AppleScript on CodeWarrior   -   Christian Schmitz
    Re: AppleScript on CodeWarrior   -   Bjorn Eiriksson
     Re: AppleScript on CodeWarrior   -   Christian Schmitz
    Re: AppleScript on CodeWarrior   -   Eric Baumgartner
     Re: AppleScript on CodeWarrior   -   Björn Eiríksson <b

AppleScript on CodeWarrior
Date: 08.06.05 23:06 (Wed, 8 Jun 2005 22:06:06 +0000)
From: Björn Eiríksson <b
Does anyone know the command to make CodeWarrior Build current Target
from a AppleScript and its parameters ?

I managed to get AppleScript to Launch CodeWarrior, Open up a Project
and Select Correct Target within the project, but cant find the command
+ parameters to build current target.

Thanks

Re: AppleScript on CodeWarrior
Date: 08.06.05 23:37 (Wed, 8 Jun 2005 22:37:50 +0000)
From: Björn Eiríksson <b
I solved it by sending a Command M apple event to it, but if someone
knows the "correct way" then that would still be nice.

Thanks

On 8.6.2005, at 22:06, Björn Eiríksson wrote:

> Does anyone know the command to make CodeWarrior Build current Target
> from a AppleScript and its parameters ?
>
> I managed to get AppleScript to Launch CodeWarrior, Open up a Project
> and Select Correct Target within the project, but cant find the
> command + parameters to build current target.
>
> Thanks
>
> --
> ______________________________________________________________________
> Björn Eiríksson <email address removed>
> Einhugur Software
> http://www.einhugur.com/
> ______________________________________________________________________
> Einhugur Software has sold its products in 47 countries world wide.
> ______________________________________________________________________
> For support: <email address removed>
> To post on the maillist: <email address removed>
> _______________________________________________
> Unsubscribe or switch delivery mode:
> <http://www.realsoftware.com/support/listmanager/>
> Search the archives of this list here:
> <http://support.realsoftware.com/listarchives/lists.html>

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

Re: AppleScript on CodeWarrior
Date: 09.06.05 21:33 (Thu, 9 Jun 2005 22:33:55 +0200)
From: Christian Schmitz
Björn Eiríksson <<email address removed>> wrote:

> Does anyone know the command to make CodeWarrior Build current Target
> from a AppleScript and its parameters ?

For me, I'd prefer to try the command line compilers from CodeWarrior to
automate the build process on my own.

What do you think?

Mfg
Christian

--

Re: AppleScript on CodeWarrior
Date: 09.06.05 22:48 (Thu, 9 Jun 2005 21:48:03 +0000)
From: Bjorn Eiriksson

On Jun 9, 2005, at 8:33 PM, Christian Schmitz wrote:

> For me, I'd prefer to try the command line compilers from
> CodeWarrior to
> automate the build process on my own.
>
> What do you think?

For me CodeWarrior is dead, so I don't want to build from
CodeWarrior, I for example wont buy CodeWarrior 10 just to
get a IDE that runs on Intel Mac to compile PEF. I see CodeWarrior
as a legacy thing that should be put out in a corner and have it
remote compile what is needed until it slowly fades out and wont be
needed any more (when OS 9 support is a thing of the past and when
PEF is history)

The problem large, before we had CodeWarrior which built everything.
Then Linux was a exception and had to be built separately which
dramatically increases cost of plugin development. CodeWarrior was
already dead on Windows and already had troubles with some Windows
API's (such as GDI+).

So the way I see it now is that plugins will need to be built like this:

Old CodeWarrior:
* MacOS Classic PPC (For a while until Classic support will be a
thing of the past)
* PEF (For a while until it will be forgotten)

XCode:
* Mach-O PPC
* Mach-O x86

GCC (On Linux)
* Linux x86 // Could possibly be done in XCode at some point,
not sure I would want to go through that trouble.

Visual Studio
* Windows x86. (I don't think GCC or other tools will ever be
good option here, MS keeps making API´s that
are difficult for compilers to use, CW had a lot of trouble
keeping up and in the end did not manage to do so)

So I vision that it it will go in this direction over the next year
or two. (Clearly it will increase cost and complexity of plugin
development a lot). Good automation could help reducing that cost,
but I don't think that automation should or may come from within
CodeWarrior since CodeWarrior is the sinking ship in the equation)

We have already taken some research steps on how to create a
universal build system to deal with this since the Visual Studio part
has been clear for quite a while although I have not started using
Visual Studio in any way in real plugin projects yet.

Björn
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

Re: AppleScript on CodeWarrior
Date: 10.06.05 21:56 (Fri, 10 Jun 2005 22:56:33 +0200)
From: Christian Schmitz
Bjorn Eiriksson <<email address removed>> wrote:

> So I vision that it it will go in this direction over the next year
> or two. (Clearly it will increase cost and complexity of plugin
> development a lot). Good automation could help reducing that cost,
> but I don't think that automation should or may come from within
> CodeWarrior since CodeWarrior is the sinking ship in the equation)

Well, ok.
I'll try the same except that I want to use Codewarriors command line
compilers, so I can write scripts which use gcc for mach-o and cw for
PEF stuff on my Mac.

Run remotely (extra box or VPC) the Visual C command line tools and the
linux gcc.

(the linux stuff already works nice ;-)

Mfg
Christian

Re: AppleScript on CodeWarrior
Date: 09.06.05 18:58 (Thu, 9 Jun 2005 10:58:54 -0700)
From: Eric Baumgartner
>From: Bj?rn Eir?ksson <<email address removed>>
>Date: Wed, 8 Jun 2005 22:06:06 +0000
>
>Does anyone know the command to make CodeWarrior Build current Target
>from a AppleScript and its parameters ?
>
>I managed to get AppleScript to Launch CodeWarrior, Open up a Project
>and Select Correct Target within the project, but cant find the command >
>+ parameters to build current target.

Something like this? (This works in CW IDE 4.2.6, I'm a bit behind.)

tell application "CodeWarrior IDE 4.2.6"
tell project document 1
Set Current Target "pluginPPC"
with timeout of 120 seconds -- however long the build is expected to take
Make Project
end timeout
end tell
end tell

Credit for this approach here:
http://groups-beta.google.com/group/comp.sys.mac.programmer.codewarrior/browse_thread/thread/be524ce197b4efd2/e4d52b974cccdc7b?q°ild+codewarrior+applescript&rnum0hlà#e4d52b974cccdc7b

--

Re: AppleScript on CodeWarrior
Date: 10.06.05 01:34 (Fri, 10 Jun 2005 00:34:55 +0000)
From: Björn Eiríksson <b
Thanks I will try that.

Björn

On 9.6.2005, at 17:58, Eric Baumgartner wrote:

>> From: Bj?rn Eir?ksson <<email address removed>>
>> Date: Wed, 8 Jun 2005 22:06:06 +0000
>>
>> Does anyone know the command to make CodeWarrior Build current
>> Target=20
>> from a AppleScript and its parameters ?
>>
>> I managed to get AppleScript to Launch CodeWarrior, Open up a
>> Project=20
>> and Select Correct Target within the project, but cant find the
>> command=20=
>>
>> + parameters to build current target.
>>
> Something like this? (This works in CW IDE 4.2.6, I'm a bit behind.)
>
> tell application "CodeWarrior IDE 4.2.6"
> tell project document 1
> Set Current Target "pluginPPC"
> with timeout of 120 seconds -- however long the build is
> expected to take
> Make Project
> end timeout
> end tell
> end tell
>
> Credit for this approach here: http://groups-beta.google.com/group/
> comp.sys.mac.programmer.codewarrior/browse_thread/thread/
> be524ce197b4efd2/e4d52b974cccdc7b?q=build+codewarrior
> +applescript&rnum=3&hl=en#e4d52b974cccdc7b
>
> --
> Eric Baumgartner
> _______________________________________________
> Unsubscribe or switch delivery mode:
> <http://www.realsoftware.com/support/listmanager/>
> Search the archives of this list here:
> <http://support.realsoftware.com/listarchives/lists.html>

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>