• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: -weak_framework CHUD
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: -weak_framework CHUD


  • Subject: Re: -weak_framework CHUD
  • From: Lyndsey <email@hidden>
  • Date: Tue, 16 May 2006 17:37:47 -0400
  • Thread-topic: -weak_framework CHUD

On 5/15/06 4:20 PM, "Lyndsey" <email@hidden> wrote:
> After researching CHUD and controlling an application's profiling using the
> CHUD APIs, I have been trying to get our application to use these APIs in
> our profile configuration. However, I am running into difficulties which I
> am hoping you may be able to help me with.

Well, I now have the PowerPC (Mac OS X 10.3.9) portion building. For your
future reference, I had not wrapped my extern function declarations in the
extern "C" bits:

#ifdef __cplusplus
    extern "C" {
#endif

extern int chudInitialize(void) __attribute__((weak_import));

extern int chudStopRemotePerfMonitor(void) __attribute__((weak_import));

extern int chudStartRemotePerfMonitor(char* label)
__attribute__((weak_import));

extern int chudAcquireRemoteAccess(void) __attribute__((weak_import));

extern int chudReleaseRemoteAccess(void) __attribute__((weak_import));

extern int chudCancelRemotePerfMonitor(void) __attribute__((weak_import));

extern int chudRegisterAsRemotePerfMonitor(void)
__attribute__((weak_import));

extern int chudMarkPID(pid_t pid, int markflag)
__attribute__((weak_import));

extern void chudCleanup(void) __attribute__((weak_import));

extern int chudIsInitialized(void) __attribute__((weak_import));

extern char* chudGetStatusStr(void) __attribute__((weak_import));

#ifdef __cplusplus
    }
#endif

I also set up the search paths as such:

OTHER_LDFLAGS = -L$(CHUD_FRAMEWORK_SEARCH_PATHS_$(CURRENT_ARCH))
-F$(CHUD_FRAMEWORK_SEARCH_PATHS_$(CURRENT_ARCH)) -lOurLibrary
-weak_framework CHUD

CHUD_FRAMEWORK_SEARCH_PATHS_i386 = /System/Library/PrivateFrameworks
CHUD_FRAMEWORK_SEARCH_PATHS_ppc =
/Developer/SDKs/MacOSX10.3.9.sdk/System/Library/Frameworks


> /usr/bin/ld: can't locate framework for: -framework CHUD
> collect2: ld returned 1 exit status

Even though PowerPC builds, Intel does not with the above error that it
cannot find the CHUD framework.

I thought that perhaps -F/System/Library/PrivateFrameworks &
-L/SystemLibrary/PrivateFrameworks was the correct way to tell Xcode how to
find the framework, but it doesn't work. How should I approach this?

Thanks for any and all suggestions.

Sincerely,
Lyndsey Ferguson

--

Lyndsey Ferguson
Software Engineer
email@hidden

VectorWorks 12
Go from life without 12 to life without limits.

Visit http://www.vectorworks.net for more information.

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Why is CHUD not being found? [was -weak_framework CHUD]
      • From: Lyndsey <email@hidden>
References: 
 >-weak_framework CHUD (From: Lyndsey <email@hidden>)

  • Prev by Date: Re: Viewing and Editing Anonymous Namespace Variables
  • Next by Date: Re: Viewing and Editing Anonymous Namespace Variables
  • Previous by thread: -weak_framework CHUD
  • Next by thread: Re: Why is CHUD not being found? [was -weak_framework CHUD]
  • Index(es):
    • Date
    • Thread