• R/O
  • R/O (HTTP)
  • R/W (SSH)
  • R/W (HTTPS)

common_source_project-fm7: Zusammenfassung des Repository

Common Source Code Project for Qt (a.k.a for FM-7).

Neueste Commits RSS

Rev. Zeit Autor Nachricht
d4c1b25 2017-03-23 11:55:47 K.Ohta master [UI][Qt] Update USING_FLAGS.
0f42cf7 2017-03-23 11:54:30 K.Ohta [BUILD][WIN32] Fix FTBFS
a5018bd 2017-03-23 02:25:26 K.Ohta [DOC] Update documents to Upstream 2017-03-20.
153861f 2017-03-23 02:21:12 K.Ohta [DOC] Update upstream's readme.
ae87c2e 2017-03-23 02:16:36 K.Ohta [BUILD] Update batch files.
5d3bc69 2017-03-23 02:15:50 K.Ohta [WIN32][Qt] Fix FTBFS with ZLIB.
aebf110 2017-03-22 21:47:39 K.Ohta [VM] Merge Upstream 2017-03-20.
a7566e6 2017-03-22 21:46:30 K.Ohta [UI][Qt] Update qt/machines/ .
ee8c85e 2017-03-22 21:45:42 K.Ohta [Build][CMake] Add supporting for ZLIB.
bee2216 2017-03-22 21:45:05 K.Ohta [UI][OSD][Qt] Prepare to support Upstream 2017-03-20.


Name Rev. Zeit Autor Nachricht
master d4c1b25 2017-03-23 11:55:47 K.Ohta [UI][Qt] Update USING_FLAGS.


** Qt porting for Common Source Code Project **
                                           Sep 09, 2016
	      K.Ohta <whatisthis.sowhat _at_ gmail.com>

0. About
   This package is Qt5 porting of Common Source Code Project (CSP).
   Building with GNU/Linux(64bit) and MinGW(32bit Windows).
1. Background
   Common Source Code Project (CSP) is good emulator writing.
   But codes are specified to M$ Visual C.
   I'm using GNU/Linux, and I starting to apply FM-7(or later).
   So, I start to port to GNU/Linux and using Qt4.
   * Note: You can build with MinGW32 and Qt 5.5.1(for MinGW).

   * TIPS: If emufoo.exe don't show screen drawing, set environment 
           variable QT_OPENGL to software (i.e. Using Windows as VirtualBox's gueat OS).
2. What you need at least:
   a. Qt5 (neither Qt3 and Qt4) toolkit.
   b. Some OpenGL implementation, maybe at leaset OpenGL v3.0 .
   c. gcc / g++ (4.7 or later? ) or llvm clang / clang++ (3.5 or later?) toolchain.
   d. SDL2 (not SDL1.x).
   e. CMake 2.8 or later.

3. How to build:
   After extracting (or git pulled) sourcecodes:
   $ cd {srctop}/source/build-cmake/{Machine name}/
   $ mkdir build
   $ cd build
   To configure:
   $ cmake ..
   $ ccmake ..

   To build:
   $ make

   To install:
   $ sudo make install

4.Qt specified notice (for non-Windows):
   ・Place R@Ms under $HOME/emu{Machine Name}/ , this directory has made
     after first using.
   ・Config file, {foo}.ini is written on $HOME/.config/emu{Machine Name}/ .
   ・Saved state file, {foo}.sta is written on $HOME/emu{Machine Name}/ .
   ・Key code conversion file is written on $HOME/.config/emu{Machine Name}/scancode.cfg .
     This file contains comma separated fields, written at hex-decimal (not decimal), 
     first is M$ Virtual Key Code,
     second is Qt's scan code.
a. I tested to build only under Debian GNU/Linux "sid".
   But, perhaps, will succed to build another GNU/Linux OSs or BSD OS variants.
   * On windows, using MinGW is already okay.
   * Cross building with GNU/Linux's MinGW32 and Qt5.5.1 (for MinGW) is available. 
     Modify and use build-cmake/config_build_cross_win32.sh and related *.cmake files.
   * And, you can also build with M$ Visual Studio 2013 or 2015.
  b. Now, I using Qt5 as toolkit, because authors of Qt announced
     "Qt4 is obsolete, will be updated no longer".

  c. All of virtual machines of upstream (@Dec 17, 2015) are already ported to Qt.
  d. Now using GCC-5.2 with Link Time Optimize to build for distrubuted binaries.

6. Upstream repositry:
7. Upstream (Takeda Toshiya San's original code) 

Have fun!
-- Ohta.
Show on old repository browser