Hi Team, We are compiling the DBD::MariaDB and DBD::mysql packages on windows. S/w's Using perl5.24.1 and VC++ 2015.
Arguments :
perl Makefile.PL --cflags=-IC:\mysql\include --libs="-LC:\mysql\lib -lmysqlclient" --testdb=vms --testuser=root --testpassword=cisco@123 --testhost=127.0.0.1 --testport=3306
Problem statement :
Cannot find the file 'mariadb_config' nor 'mysql_config'! Your execution PATH doesn't seem not contain the path to mariadb_config or mysql_config. Resorting to guessed values! : Checking if libs and header files are available for compiling... Can't link/include C library 'windows.h', 'winsock.h', 'mysql.h', 'mysqlclient', aborting. As i compiled DBI same issue. Not sure what is the expectation i am missing here. Kindly help I searched many does resolved the issue. And where can i get the above config files. Thanks, Anitha.S

In reply to DBD:Mysql compilation failed on windows by pesubbia

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.