Is there a way to use svn global command line options when using svnant?
Example option: '--no-auth-cache'
We use javahl as svn lib.
svnant documentation does not mention such options
Related
What is the -i option for "Go tool arguments" in GoLand's Run/Debug Configurations window?
Taken from go help build:
The -i flag installs the packages that are dependencies of the target.
The -i flag is deprecated. Compiled packages are cached automatically.
You will get a message while uses it:
go build: -i flag is deprecated
The -i build flag
The -i flag accepted by go build, go install, and go test is now
deprecated. The -i flag instructs the go command to install packages
imported by packages named on the command line. Since the build cache
was introduced in Go 1.10, the -i flag no longer has a significant
effect on build times, and it causes errors when the install directory
is not writable.
It is from Go 1.16 Release Notes
So its presence doesn't matter now and you can remove this flag from arguments
I know this might be a dumb question, but I cannot figure out how to install and use Apache Daffodil. Any help would be appreciated. I cannot find anything helpful. Thank you!
Download apache Daffodil from below url
https://downloads.apache.org/daffodil/3.0.0/src/apache-daffodil-3.0.0-incubating-src.zip
The binary Daffodil releases contain a /bin directory that contains two scripts: daffodil.bat for Windows and daffodil for Linux. These files must be executed on the command line.
Extract downloaded zip
Path of bin directory export as environment variables.
After that you can verify its installed or not via below cammand it will show the version of daffodil
daffodil --version
Global Options
-d, --debug [FILE]
Enable the interactive debugger. See the Interactive Debugger documentation for more information.
The optional FILE argument contains a list of debugger commands that are provided to the debugger as they were typed by the user.
This option cannot be used with the --trace option.
-t, --trace
Enable a trace mode. This mode prints out helpful information during every stage of parsing.
This option cannot be used with the --debug option.
-v, --verbose
Enable verbose mode and increment verbosity level. Each additional v provides a new level of information.
--version
Display the version of Daffodil.
--help
Display help message.
I have cmake target which runs a setup.exe on windows which installs a tool using add_custom_target as follows
# TOOL_TEMP_INSTALL_PATH is the installation path which is set earlier in cmake
add_custom_target(
install_tool
COMMAND ${TOOL_TEMP_DIR}/setup.exe /DIR=${TOOL_TEMP_INSTALL_PATH}
)
After the installation, I want to replace text in a configuration file located at ${TOOL_TEMP_INSTALL_PATH}/tool.ini replacing a line of text "LICENSE_FILE=Enter License server" with "LICENSE_FILE=30309#server"
Following commands will achieve this but this needs to be run after install_tool target is built.
file(READ "${TOOL_TEMP_INSTALL_PATH}/tool.ini" filedata)
string(REGEX REPLACE "LICENSE_FILE=Enter License server here"
"LICENSE_FILE=30309#server" filedata "${filedata}")
file(WRITE "${TOOL_TEMP_INSTALL_PATH}/tool.ini" "${filedata}")
How can I add these commands as a dependency to install_tool? Or is there a better way to achieve this on windows?
Since you want to run two things in order as part of the same target, you can use multiple COMMAND entries in the same target. The difficulty is that COMMAND can't handle CMake code, but only system commands. The typical solution is to call CMake in a subshell on a script file:
COMMAND ${CMAKE_COMMAND} -P path_to_script
So, place your file modification commands in a file in your source tree called license-install.cmake, and add another COMMAND to your add_custom_target
Hint: You might consider add_custom_command instead, so you can specify a file in the installed tree as a dependency. This will allow CMake to see the installed tool as a build product, and to skip the install step if the tool is already installed. You'll still need an add_custom_target with a dependency on your command output to hook it in correctly.
I've built the release version of OpenSSL 1.1.1c libraries without a problem, but I cannot create the Debug version.
According the documentation I used:
perl Configure --debug VC-WIN64A
However the Perl % (ActiveState) doesn't recognize the argument debug.
When I use -d, the build alone will switch to the debug execution mode.
Somewhere on Internet I found the form:
perl Configure debug-VC-WIN64A
However, I couldn't confirm it with the documentation.
What is the proper format for the Perl?
-d does not work with windows builds... The original poster had it correct, he just had the parameters in the wrong order...
On Windows, to build a debug version, you do it like:
perl Configure VC-WIN64A --debug
I just verified it just now, as I'm building 1.1.1l as we speak. Omitting that flag, defined NDEBUG, but specifying that flag defines DEBUG. Original poster specified --debug before VC-WIN64A, but it must be specified after.
according the documentation I used:
perl Configure --debug VC-WIN64A
However the Perl % (ActiveState) doesn't recognize the argument debug.
When I use -d, the build alone will switch to the debug execution
mode.
According to Compilation and Installation on the OpenSSL wiki, you should use -d. See Configure Options
Somewhere on Internet I found
perl Configure debug-VC-WIN64A
however, I couldn't confirm it with the documentation.
Use Configure LIST to show the targets.
$ ./Configure LIST | grep VC
VC-CE
VC-WIN32
VC-WIN32-ARM
VC-WIN32-ARM-UWP
VC-WIN32-ONECORE
VC-WIN32-UWP
VC-WIN64-ARM
VC-WIN64-ARM-UWP
VC-WIN64A
VC-WIN64A-ONECORE
VC-WIN64A-UWP
VC-WIN64A-masm
VC-WIN64I
You might also be interested in NOTES.WIN, which are the build and install notes for Windows. The notes do not list --debug.
It looks like --debug is detailed in INSTALL file. --debug works on Linux for OpenSSL 1.1. Maybe it does not work on Windows, or maybe it used to work with a version like OpenSSL 1.0.
(I don't have a Windows machine with Perl, so I can't run the tests for you).
I install cygwin frequently enough that it would be handy to have the process automated. Specifically, I want to be able to specify ahead of time the packages that I want to install, so that I don't have to remember them at install-time. Is there any way to do this?
Yes, you can. Assuming you haven't installed Cygwin yet, bash isn't available, so you have to use a CMD script. Here's an example:
setup-x86.exe ^
--quiet-mode ^
--packages ^
aria2,^
atool,^
autoconf,^
...
xmlstarlet,^
zip
and add other packages to the list. The caret (^) character at the end of every line is the line continuation character in CMD scripts. The list of package names is comma-delimited, which is what the --packages option expects, although that's not documented.
You can run setup-x86.exe --help, or see the Cygwin FAQ, to read about the available command line options for setup.
If you name this script, say, setup.bat or setup.cmd, and put it in the same directory as setup-x86.exe, then you can run it to get a one-click install of Cygwin with all of the packages you want.
Note also that you'll have to specify the --site and --root options for a fresh install, or it will kick out of "quiet mode" and prompt the user anyway.
apt-cyg is similar to what I was looking for, although it requires a pre-existing cygwin install with a few non-default packages.
I don't know if you can script it, but I found a 'how-to' on making a custom package directory and the installer to go with it. This way, you can have all the packages you need and have the installer pre-selected.
You can find that article here.