$qmake litecoinx-qt.pro RELEASE=1 USE_UPNP=1 -config release QMAKE_LFLAGS+=
"-static-libgcc -static-libstdc++" BOOST_INCLUDE_PATH=C:/MinGW/msys/1.0/local/include
BOOST_LIB_PATH=C:/MinGW/msys/1.0/local/lib BOOST_LIB_SUFFIX=-mgw46-mt-s-1_54
$make -f Makefile.Release
"-static-libgcc -static-libstdc++" BOOST_INCLUDE_PATH=C:/MinGW/msys/1.0/local/include
BOOST_LIB_PATH=C:/MinGW/msys/1.0/local/lib BOOST_LIB_SUFFIX=-mgw46-mt-s-1_54
$make -f Makefile.Release
You need to include error logs if your having a problem compiling it.
You are probably better off making your makefile and qt.pro include the flags and library paths manually, it will also help you greatly to understand both Makefiles and the qt pro configuration files, they are not that complex and spending an hour researching them will help you greatly in compiling(and developing if that is your goal); some of the issues you may be experiencing:
-Almost every coin also has more dependencies than the ones you have there, I imagine litecoinx is no different. In addition to boost you likely need to tell it most of the following are: berkeleydb, openssl, protobuf, libpng, qrencode etc are.
-Not just the qmake needs to know where those libraries are, the makefile needs to know as well.
-That is an old version of boost, it is encouraged to make sure your libraries and other dependencies are up to date, especially OpenSSL. That being said, even if they are not, you need to make sure the version you have installed, is the same as you are entering above.
-Is your build static? The qt file may or may not be designed to be for static compilation, you may have to add additional flags if it isn't yet, or remove them if they are there but your qt isn't compiled to support static builds.
-Typically, you would run make -f Makefile.Release first, then compile the qt afterwards.
That being said, im not sure if this forum section is the right place for this kind of support, outside of a few threads with more elaborate topics surrounding.
Im sure your anxious to 'just get it going' whatever it is, but learning about compilation flags, dependencies, makefiles etc will only take you an hour or so, and save you alot more time then your sure to spend now and in the future trying to figure out issues like you are likely experiencing now.
