[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnu-arch-users] What's the rationale behind the cmd-build-config.c
From: |
Matthew Dempsky |
Subject: |
Re: [Gnu-arch-users] What's the rationale behind the cmd-build-config.c restrictions? |
Date: |
Fri, 28 Jan 2005 14:55:03 -0600 |
User-agent: |
Gnus/5.1007 (Gnus v5.10.7) Emacs/21.3 (gnu/linux) |
Rob Browning <address@hidden> writes:
> In cmd-build-config.c we have:
>
> if (!arch_valid_config_name (config))
> {
> safe_printfmt (2, "%s: invalid config name (%s)\n",
> argv[0], config);
> exit (2);
> }
>
> tree_root = arch_tree_root (0, dir, 0);
>
> if (!tree_root)
> {
> safe_printfmt (2, "%s: not in project tree (%s)\n",
> argv[0], dir);
> exit (1);
> }
>
> What's the rationale behind these restrictions?
Mostly it's because the config is built relative to the tree root. I
suppose you could add a -d option (or something) for where the tree
root should be located instead, and then it's no longer necessary to
be in an arch tree.