Re: The ".." in "meson setup .."

"Rainer Fiebig" ([email protected] via blfs-support Mailing List) <[email protected]> Tue, 28 Apr 2026 23:38:32 +0200
Newsgroups gmane.linux.lfs.beyond.support
Message-ID <[email protected]>
This is a multi-part message in MIME format...

------------=_1777412339-1253-26833
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

Am 28.04.26 um 14:46 schrieb Rainer Fiebig ([email protected] via
blfs-support Mailing List):
> I've been wondering for a while now what the two dots in
> 
> meson setup ..   \
> 
> might be good for.  Perhaps everybody else knows but I don't and I
> couldn't find an explanation in the books nor in the
> meson-documentation.  My tests suggest that they are not necessary,
> meaning that the following forms would be equivalent:
> 
> meson setup ..   \
> meson setup      \ 	
> 
> So, _if_ the dots serve no other purpose than to fill space: wouldn't it
> be better to leave them out?  For reasons of clarity and simplicity?
> Thanks.
> 
> Rainer
> 

Thanks everybody!  That ".." simply stands for "parent directory" seems
correct, as "meson setup" has positional arguments:

meson setup --help
[...]
positional arguments:
  builddir
  sourcedir
[...]

The "builddir" probably doesn't have to be specified if it's the working
directory ("build" in our case).

Nevertheless: I just built xorg-server and NetworkManager, each with
both above mentioned forms and from freshly unpacked sources and a
DESTDIR-installation.  And there were no problems.  All four builds
succeeded as usual and the test-results were identical.  Just to be sure
about the positional arguments, I also built xorg-server with

meson setup $(pwd) ..   \

and that also worked. ;)

Alright, case settled and closed, I think.  Thanks again for your input!

Rainer



------------=_1777412339-1253-26833
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-support
Unsubscribe: See the above information page

------------=_1777412339-1253-26833--