Revision 976aaedca0c6f64b37f4241bf06fa7ab06095986 authored by Johannes Schindelin on 29 July 2019, 20:08:12 UTC, committed by Junio C Hamano on 29 July 2019, 21:51:43 UTC
The entire idea of generating the VS solution makes only sense if we
generate it via Continuous Integration; otherwise potential users would
still have to download the entire Git for Windows SDK.

If we pre-generate the Visual Studio solution, Git can be built entirely
within Visual Studio, and the test scripts can be run in a regular Git
for Windows (e.g. the Portable Git flavor, which does not include a full
GCC toolchain and therefore weighs only about a tenth of Git for
Windows' SDK).

So let's just add a target in the Makefile that can be used to generate
said solution; The generated files will then be committed so that they
can be pushed to a branch ready to check out by Visual Studio users.

To make things even more useful, we also generate and commit other files
that are required to run the test suite, such as templates and
bin-wrappers: with this, developers can run the test suite in a regular
Git Bash after building the solution in Visual Studio.

Note: for this build target, we do not actually need to initialize the
`vcpkg` system, so we don't.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
1 parent 384a61b
Raw File
tr2_cfg.h
#ifndef TR2_CFG_H
#define TR2_CFG_H

/*
 * Iterate over all config settings and emit 'def_param' events for the
 * "interesting" ones to TRACE2.
 */
void tr2_cfg_list_config_fl(const char *file, int line);

/*
 * Emit a "def_param" event for the given key/value pair IF we consider
 * the key to be "interesting".
 */
void tr2_cfg_set_fl(const char *file, int line, const char *key,
		    const char *value);

void tr2_cfg_free_patterns(void);

#endif /* TR2_CFG_H */
back to top