[darwinbuild-dev] Error: TargetConfig not defined

[pdub]

I beleive that you will find that the 'TargetConfig not defined' error is coming from the build file

ReleaseControl/Common.make

in the CoreOSMakefiles project.

The relevant code in Common.make is

install:: _targetconfig install_headers build

_targetconfig::
	@PRODUCT="`tconf --product 2>/dev/null`" ; \
	if [ -z "$$PRODUCT" ]; then \
	echo "Error: TargetConfig not defined" ; exit 1 ; \
	else echo "TargetConfig: $$PRODUCT" ; fi

The command tconf --product tries to find a suitable plist and extract the value of the TargetConfigProduct key from the plist, printing it to stdout.

tconf searches for the plist to use, based on the environment variables SDKROOT and RC_TARGET_CONFIG. It tries to find, in order:

1) $(SDKROOT)/usr/share/TargetConfigs/Default.plist
2) /usr/share/TargetConfigs/$(RC_TARGET_CONFIG).plist
3) /usr/share/TargetConfigs/Default.plist

If SDKROOT or RC_TARGET_CONFIG is not defined, tconf skips looking for the respective plist. tconf uses the first file that is found, and parses as a proper plist, and has the TargetConfigProduct key, to print the value of the key to stdout and return EXIT_SUCCESS. If no suitable file is found, it prints nothing and returns EXIT_FAILURE.

Common.make is invoked by BSDCommon.make, GNUSource.make, and BSD.make. The BSDCommon.make, GNUSource.make, and BSD.make files do not set the value of SDKROOT or RC_TARGET_CONFIG. Most of the Darwin project makefiles don't set them either. (Notable exceptions are TargetConfig-6 and TargetConfig-12.1, which set RC_TARGET_CONFIG to MacOSX if it is not already defined.)

Thus tconf is usually looking for /usr/share/TargetConfigs/Default.plist. There is no Default.plist in the TargetConfig source package.

TargetConfig installhdrs installs MacOSX.plist
TargetConfig_host installhdrs installs a link from Default.plist to MacOSX.plist (actually $(RC_TARGET_CONFIG).plist), and other stuff.
TargetConfig install only builds the tconf program (and some feature scripts). It does not install any plist file or link.

One fix is to have binary roots for TargetConfig headers and TargetConfig_host headers as will as TargetConfig, and load all three (if darwinbuild is happy with loading an XXX.hdrs root as well as XXX root).

Another alternative is to have darwinbuild routinely initialize the environment variable RC_TARGET_CONFIG to MacOSX.

All of the above is based on my reading of the TargetConfig-12.1 source files and my experience exploring the same issues in TargetConfig-6. I can't upgrade my development system to Snow Leopard for a while *sigh*. Still, I hope this is helpful.

Cheers,
pdub

--- On Thu, 9/24/09, William Siegrist <wsiegrist at apple.com> wrote:

> From: William Siegrist <wsiegrist at apple.com>
> Subject: Re: [darwinbuild-dev] Error: TargetConfig not defined
> To: "Tony Morales" <tmorales at covad.net>
> Cc: "DarwinBuild" <darwinbuild-dev at lists.macosforge.org>
> Date: Thursday, September 24, 2009, 2:28 PM
> tconf is crashing, but I have not
> isolated the cause yet. This is a problem for many projects,
> so its on the top of my list to fix. Thanks for reporting
> it.
> 
> -Bill
> 
> 
> 
> On Sep 24, 2009, at 8:01 AM, Tony Morales wrote:
> 
> > I'll try copying over xcrun and see what happens.
> > 
> > However, project apr doesn't use xcodebuild or xcrun
> to build, as far as I can tell.  What does the
> TargetConfig not defined error mean when I try and build
> apr?  It appears that the TargetConfig root was
> downloaded so I shouldn't need to rebuild it.
> > 
> > Tony
> > 
> > 
> > On Sep 24, 2009, at 7:43 AM, William Siegrist wrote:
> > 
> >> On Sep 24, 2009, at 7:16 AM, Tony Morales wrote:
> >> 
> >>> When attempting to build project apr on 10A432
> using 10A432 or 10B504, I get the following in my build
> log:
> >>> 
> >>> Error: TargetConfig not defined
> >>> make[1]: *** [_targetconfig] Error 1
> >>> make: *** [install] Error 1
> >>>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>> BUILD TIME: 0h 0m 1s
> >>> EXIT STATUS: 2
> >>> 
> >>> What does this mean?  If I try to build
> project TargetConfig, then I get the following in my build
> log:
> >>> 
> >>> make: xcrun: Command not found
> >>> Error: TargetConfig not defined
> >>> make: *** [_targetconfig] Error 1
> >>>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>> BUILD TIME: 0h 0m 2s
> >>> EXIT STATUS: 2
> >>> 
> >>> This is all using the latest svn rev (575).
> >>> 
> >> 
> >> 
> >> Snow Leopard introduced the use of "xcrun" from
> within Makefiles which ends up invoking xcodebuild to
> determine where certain tools are found during the build
> process. It basically means we now have a 3rd class of
> projects after makefile-based and xcode-based, and it needs
> to be treated differently. I'm still working on a solution.
> You can experiment with -nochroot or with copying some Xcode
> binaries into the build root, but we'll have a working
> solution eventually.
> >> 
> >> -Bill
> >> 
> >> 
> >> 
> > 
> 
> _______________________________________________
> darwinbuild-dev mailing list
> darwinbuild-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/darwinbuild-dev
>