On Jun 21, 2010, at 6:39 AM, Andrew R. Kinnie wrote:

> I guess I am not clear.  This runs fine when I am debugging it.  The Wonder 
> source is in my workspace and added to the project.  It runs and sees the 
> resulting frameworks fine in dev.  When I do an Ant build, it has no idea 
> where they are. 

Ant knows _nothing_ of your Eclipse workspace.  Ant is a totally different 
thing.


> I did not tell it any specified location for any of this stuff, other than 
> where the source for wonder was when I imported into the workspace.  

Again, this is of no use to ant.


> I don't have any idea where I tell Ant to build these frameworks separately 
> from wherever they're built by default (supposedly /Library/Frameworks, but 
> clearly they not there).  I certainly did not intentionally do so, yet they 
> are clearly not being installed there.  Am I supposed to do a separate build 
> and install of the wonder frameworks before building the app?

Yes.


> Where would I specify a location for the frameworks to be installed?  (I'd 
> rather not have to install them into /Library/Frameworks, but if I have to I 
> have to).

There is a way to change the install location, but I don't recall what it is.  
You can also manually install (e.g. copy) them from where they are built to 
where you want them installed.

For the normal /Library location, see 
http://wiki.objectstyle.org/confluence/display/WONDER/Download+Wonder+Source%2C+Build+and+Install

Chuck


> I am just looking for how I change the location of the frameworks so Ant 
> would find them, in the same way the dev build mechanism does.
> 
> Sorry to be a pain.
> 
> On Jun 21, 2010, at 9:25 AM, David LeBer wrote:
> 
>> 
>> On 2010-06-21, at 9:19 AM, Andrew R. Kinnie wrote:
>> 
>>> Where do I specify this?
>> 
>> Specify what?
>> 
>>> I have not changed much of anything from the defaults, except in 
>>> development I added the wonder frameworks from the checked out head of 
>>> wonder.  (I imported into my project with a specified path 
>>> /Developer/Wonder/Wonder_Head/)
>>> 
>>> So I gather importing the project source into my workspace does not tell 
>>> anything to the build configuration?
>> 
>> You don't need to do anything with the build configuration.
>> 
>> You just need to make sure that the Wonder frameworks are installed in 
>> /Library/ (if you are using a standard install location) or [my webobjects 
>> tree path]/Library/ if you are doing something custom.
>> 
>>> On Jun 21, 2010, at 9:14 AM, David LeBer wrote:
>>> 
>>>> Doing an ant build expects all of the dependent frameworks to be built in 
>>>> the specified local Library directory. So does ERExtensions.framework 
>>>> exist in [whatever path is appropriate]/Library/?
>>>> 
>>>> ;david
>>> 
>> 
>> ;david
>> 
>> --
>> David LeBer
>> Codeferous Software
>> 'co-def-er-ous' adj. Literally 'code-bearing'
>> site:        http://codeferous.com
>> blog:        http://davidleber.net
>> profile:     http://www.linkedin.com/in/davidleber
>> twitter:     http://twitter.com/rebeld
>> --
>> Toronto Area Cocoa / WebObjects developers group:
>> http://tacow.org
>> 
>> 
>> 
>> 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/webobjects-dev/chill%40global-village.net
> 
> This email sent to [email protected]

-- 
Chuck Hill             Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their overall 
knowledge of WebObjects or who are trying to solve specific problems.    
http://www.global-village.net/products/practical_webobjects







Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to