search for: liboption

I'm given to understand that the recommendation these days is to use libOption instead of cl::opt, on the grounds that it has a number of advantages including more control of which options are made available. Is there any information available on how to use libOption, any documentation or example programs? Do any existing programs use it except the clang driver programs? Tho...

Okay, that makes sense, thanks. I'll go with cl::opt, then. On Wed, Apr 20, 2016 at 8:08 AM, Sean Silva <chisophugis at gmail.com> wrote: > libOption's key feature is being able implement command line parsing > compatible with basically any program under the sun. For example, you have > control over distinguishing between `-foo` and `--foo` if you need that. > It is used in clang for command line parsing compatible cl.exe and gcc. &...

...options/Makefile.am | 3 +++ 1 file changed, 3 insertions(+) diff --git a/options/Makefile.am b/options/Makefile.am index 2f10d53..28940f1 100644 --- a/options/Makefile.am +++ b/options/Makefile.am @@ -17,6 +17,9 @@ include $(top_srcdir)/subdir-rules.mk +EXTRA_DIST = \ + key-option.pod + # liboptions.la contains guestfish code which is used in other # C tools for options parsing and a few other things noinst_LTLIBRARIES = liboptions.la -- 2.23.0

...\ -I$(top_srcdir)/lib -I$(top_builddir)/lib \ -I$(top_srcdir)/common/options -I$(top_builddir)/common/options \ -I$(top_srcdir)/common/parallel -I$(top_builddir)/common/parallel \ @@ -46,6 +47,7 @@ virt_alignment_scan_CFLAGS = \ virt_alignment_scan_LDADD = \ $(top_builddir)/common/options/liboptions.la \ $(top_builddir)/common/parallel/libparallel.la \ + $(top_builddir)/common/structs/libstructs.la \ $(top_builddir)/common/utils/libutils.la \ $(top_builddir)/lib/libguestfs.la \ $(LIBXML2_LIBS) \ diff --git a/align/scan.c b/align/scan.c index 4fa95c0a3..b9f29868c 100644 --- a/align/sca...

...nups -I$(top_builddir)/common/cleanups \ -I$(top_srcdir)/common/utils -I$(top_builddir)/common/utils \ -I$(top_srcdir)/lib -I$(top_builddir)/lib \ -I$(top_srcdir)/common/options -I$(top_builddir)/common/options \ @@ -47,6 +48,7 @@ virt_alignment_scan_LDADD = \ $(top_builddir)/common/options/liboptions.la \ $(top_builddir)/common/parallel/libparallel.la \ $(top_builddir)/common/utils/libutils.la \ + $(top_builddir)/common/cleanups/libcleanups.la \ $(top_builddir)/lib/libguestfs.la \ $(LIBXML2_LIBS) \ $(LIBVIRT_LIBS) \ diff --git a/builder/Makefile.am b/builder/Makefile.am index 5f0606c...

In file included from libopts.c:23: ./makeshell.c:138:26: warning: more '%' conversions than data arguments "unset OPT_ARG_VAL || :\n%2$s"; This is not correct. The format below uses the first argument twice and the second argument once. The "clang" analysis does not properly recognize the "1$" and "2$" modifiers. This is POSIX for a while,

...haviour is that each letter following it is treated as a different option, whereas in llvm-readobj, we get one single option (e.g. ‘readobj -abc’ would be equivalent to ‘readobj -a -b -c’, but ‘llvm-readobj -abc’ is equivalent to ‘llvm-readobj --abc’). This is at least partly related to the cl::opt/libOption issues discussed in http://lists.llvm.org/pipermail/llvm-dev/2018-October/127328.html). I'd like to propose that we fix the three switches above such that they match GNU readelf's interpretation, and to change short-option handling similarly. This would inevitably result in some test churn...

Alexander, First off, CentOS7 came with cronyd. Which was very annoying because when I tried to remove it, it had 2 prereqs: anaconda initial-setup Now, I don't know why the setup program kept these 2 around. I think CentOS7 needs a bit growing up. Anyway, I disabled chrony: systemctl disable time-sync systemctl stop time-sync Then I installed ntp. However, when I started it it seems that

On Fri, Dec 12, 2014 at 09:55:12AM -0500, xaos wrote: > > Alexander, > > First off, CentOS7 came with cronyd. Which was very annoying > because when I tried to remove it, it had 2 prereqs: > anaconda > initial-setup > > Now, I don't know why the setup program kept these > 2 around. I think CentOS7 needs a bit growing up. 'initial-setup' is the program

Previous patch series was posted here: https://www.redhat.com/archives/libguestfs/2017-January/msg00059.html v2 simply extends this patch series to cover the extra directories common/edit, common/progress, common/windows and common/parallel. The only remaining item is to consider whether we should rename mllib to something else, mlcommon was my suggestion. Rich.

...g it is >> treated as a different option, whereas in llvm-readobj, we get one single >> option (e.g. ‘readobj -abc’ would be equivalent to ‘readobj -a -b -c’, but >> ‘llvm-readobj -abc’ is equivalent to ‘llvm-readobj --abc’). This is at >> least partly related to the cl::opt/libOption issues discussed in >> http://lists.llvm.org/pipermail/llvm-dev/2018-October/127328.html). >> >> I'd like to propose that we fix the three switches above such that they >> match GNU readelf's interpretation, and to change short-option handling >> similarly. Thi...

Some additional information about the setup may be of interest: I'm using CMake to generate the make files for MSYS. All appears to go well until the tools are compiled. The undefined references seem to be coming from the libraries that were just compiled: ../../lib/libLLVMBitReader.a(BitcodeReader.cpp.obj):fake:(.rdata$linkonce_ZTVN4llvm8ConstantE+0x10): undefined reference to

This patch series moves some files and directories around but is only code motion (or supposed to be). A new directory, common/, is created for all of the common code which is currently shared in random ways between parts of the project. And src/ becomes lib/ (the largest change, but mostly mechanical). In full this series makes the following changes: src/libprotocol -> common/protocol

This turned out to be rather more involved than I thought. We have lots of utility functions, spread all over the repository, with not a lot of structure. This moves many of them under common/ and structures them so there are clear dependencies. This doesn't complete the job by any means. Other items I had on my to-do list for this change were: - Split up mllib/common_utils into: -

From: Nikolay Ivanets <stenavin@gmail.com> v4 fixes issues found during code review: - whitespace-change-only hunks are removed - options are alphabetically orderred now v3 is just a spelling correction spotted by Eric Blake https://www.redhat.com/archives/libguestfs/2020-February/msg00111.html In v2 I've moved '--blocksize' parameter description into the separate file called

Hello again, In order to avoid the set jump/long jump dependency of DLLs built under Visual C++, we're trying to build the libraries and tools under LLVM-GCC so it will use DWARF exception handling instead of SJ/LJ. The problem we're running into is that the libraries that we just finished creating cannot be found later in the build process when OPT tries to build. My partner has MinGW

...s/blocksize-option.pod diff --git a/options/Makefile.am b/options/Makefile.am index 28940f1..394f668 100644 --- a/options/Makefile.am +++ b/options/Makefile.am @@ -18,7 +18,8 @@ include $(top_srcdir)/subdir-rules.mk EXTRA_DIST = \ - key-option.pod + key-option.pod \ + blocksize-option.pod # liboptions.la contains guestfish code which is used in other # C tools for options parsing and a few other things diff --git a/options/blocksize-option.pod b/options/blocksize-option.pod new file mode 100644 index 0000000..ae748be --- /dev/null +++ b/options/blocksize-option.pod @@ -0,0 +1,11 @@ +=item B&lt...

From: Nikolay Ivanets <stenavin@gmail.com> v3 is just a spelling correction spotted by Eric Blake In v2 I've moved '--blocksize' parameter description into the separate file called blocksize-option.pod so we can include it everywhere we need similar to key-option.pod. https://www.redhat.com/archives/libguestfs/2020-February/msg00099.html v1 was here:

Depends on the previous 5 patches that modified virt-rescue to work without direct mode: https://www.redhat.com/archives/libguestfs/2017-March/msg00017.html Rich.

From: Nikolay Ivanets <stenavin@gmail.com> In v2 I've moved '--blocksize' parameter description into the separate file called blocksize-option.pod so we can include it everywhere we need similar to key-option.pod. v1 was here: https://www.redhat.com/archives/libguestfs/2020-February/msg00096.html Nikolay Ivanets (1): options: add '--blocksize' option for C-based