I tested a build of the current stable sources and it seems to handle the example from the original submission correctly.

You can override the OCTAVE_LINK_DEPS value by setting it with set env:

setenv('OCTAVE_LINK_DEPS', "-lfreetype -lhdf5 -lGraphicsMagick++ -lGraphicsMagick -lz -lfftw3 -lfftw3f \
-lopengl32 -lglu32 -lfontconfig -lfreetype    -lgl2ps  -ladvapi32 -llapack -lcurl -lcholmod -lumfpack \
-lamd -lcamd -lcolamd -lccolamd -lcxsparse -lsuitesparseconfig -larpack -lqrupdate -lopenblas \
-lreadline -ltermcap  -lpcre  -lm -lgfortran -lmingw32 -lmoldname \
-lmingwex -lmsvcrt -lquadmath -lpthread -ladvapi32 -lshell32 -luser32 -lkernel32 -lpsapi -lgdi32 \
-lm -lws2_32 -lws2_32   -ladvapi32  -lws2_32 -lws2_32 -liconv")

Hi, not sure if I understand all your comments. Do i have to change a setting to get mkoctfile working ? If so, please tell me how to do this.  Thanks

That is all correct information. On a typical GNU/Linux system, the iconv function is included in glibc, so both LIBICONV and LTLIBICONV should be empty.

It is also correct that Octave builds itself using the Libtool variant LTLIBICONV, but uses the non-Libtool variant LIBICONV when embedding the string into mkoctfile.

The only thing that is incorrect about this is that Gnulib's code for checking for libiconv is embedding the fixed path to the library into LIBICONV. The logic for all of this is in Gnulib's AC_LIB_LINKFLAGS macro (lib-link.m4).

I'm not sure how libtool vs the rest works, but for reference, when looking in config.log when cross building octave for windows.

LTLIBICONV = -L/thelibpath -liconv -R/thelibpath


LIBICONV = /thelibpath/libiconv.dll.a -L/thelibpath


On my native fedora build:

LIBICONV = ''
LIBLTICONV = ''

In the config.log

configure:41844: checking how to link with libiconv
configure:41846: result: /scratch/build/mxe-octave-w64-32-stable/usr/x86_64-w64-mingw32/lib/libiconv.dll.a -L/scratch/build/mxe-octave-w64-32-stable/usr/x86_64-w64-mingw32/lib

The check for libiconv comes directly from Gnulib, but maybe there is a cache variable or an option that can be used to influence the result here.

If I specify the command
mkoctfile --link-stand-alone standalone.cc -o standalone.exe -verbose
 then got the message
g++: error: /scratch/build/mxe-octave-w64-32-stable/usr/x86_64-w64-mingw32/lib/libiconv.dll.a: No
 such file or directory

In 4.2.2 the library and include was set to the installation folder, e.g. c:\octave4.2.2\....


Code standalone.cc

#include <iostream>
#include <octave/oct.h>

int
main (void)
{
  std::cout << "Hello Octave world!\n";

  int n = 2;
  Matrix a_matrix = Matrix (n, n);

  for (octave_idx_type i = 0; i < n; i++)
    for (octave_idx_type j = 0; j < n; j++)
      a_matrix(i,j) = (i + 1) * 10 + (j + 1);

  std::cout << a_matrix;

  return 0;
}