mirror of
https://github.com/checkpoint-restore/criu
synced 2025-08-26 03:47:35 +00:00
7cd6ad5e7e
This -u option always looked wrong to me, I mean, how the hell a user is supposed to know where the hell those headers are? It took quite a while to figure out what to do with it, but the end result is -- this option is not needed at all and can easily be dropped. For finding paths to includes, there is a -I compiler option, there's no need to specify something to compel. In fact, it should know by itself where its own headers are kept (and emit -I... to cflags if needed), but that's another story which is to be told when we'll decide to pack compel as a standalone tool. For now, just add "#include <compel/compel.h>" and be done. Signed-off-by: Kir Kolyshkin <kir@openvz.org> Signed-off-by: Pavel Emelyanov <xemul@virtuozzo.com> Signed-off-by: Andrei Vagin <avagin@virtuozzo.com>
29 lines
497 B
C
29 lines
497 B
C
#ifndef COMPEL_PIEGEN_H__
|
|
#define COMPEL_PIEGEN_H__
|
|
|
|
#include <stdio.h>
|
|
#include <unistd.h>
|
|
|
|
#include <elf.h>
|
|
|
|
#include "common/compiler.h"
|
|
|
|
typedef struct {
|
|
char *input_filename;
|
|
char *output_filename;
|
|
char *prefix;
|
|
FILE *fout;
|
|
} piegen_opt_t;
|
|
|
|
extern piegen_opt_t opts;
|
|
|
|
#define pr_out(fmt, ...) \
|
|
do { \
|
|
if (opts.fout) \
|
|
fprintf(opts.fout, fmt, ##__VA_ARGS__); \
|
|
} while (0)
|
|
|
|
extern int handle_binary(void *mem, size_t size);
|
|
|
|
#endif /* COMPEL_PIEGEN_H__ */
|