d6baf09fe0
Most modules are direct implementations of openssl application sub-commands, but some constitute a support library, which can be used by more than one program (and is, incidently, by test/uitest). For practical purposes, we place the support library modules in a private, static library. Finally, there are some modules that don't have direct references in the rest of the apps code, but are still crucial. See them as some kind of extra crt0 or similar for your platform. Inspiration from David von Oheimb Reviewed-by: Rich Salz <rsalz@openssl.org> (Merged from https://github.com/openssl/openssl/pull/5222)
22 lines
649 B
Perl
22 lines
649 B
Perl
#! /usr/bin/perl
|
|
|
|
use Config;
|
|
|
|
# Check that the perl implementation file modules generate paths that
|
|
# we expect for the platform
|
|
use File::Spec::Functions qw(:DEFAULT rel2abs);
|
|
|
|
if (!$ENV{CONFIGURE_INSIST} && rel2abs('.') !~ m|\\|) {
|
|
die <<EOF;
|
|
|
|
******************************************************************************
|
|
This perl implementation doesn't produce Windows like paths (with backward
|
|
slash directory separators). Please use an implementation that matches your
|
|
building platform.
|
|
|
|
This Perl version: $Config{version} for $Config{archname}
|
|
******************************************************************************
|
|
EOF
|
|
}
|
|
|
|
1;
|