• 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
7a70a00 2017-02-18 01:12:48 K.Ohta master [DOC] Update Issues.See http://hanabi.2ch.net/test/read.c...
c1f58d4 2017-02-15 06:22:29 K.Ohta [BUILD][CMake][VM] Add TK-85.
34a59b4 2017-02-15 06:07:04 K.Ohta [VM][N5200] Fix FTBFS.
dde3963 2017-02-15 06:05:24 K.Ohta [UI][Qt][Draw] Update button api: Use *real* image, not t...
e1c30a8 2017-02-13 02:01:36 K.Ohta [Build][Win32][VM] Prepare to fix FTBFS.
61b9579 2017-02-13 01:59:42 K.Ohta [Qt][OpenGL] Workaround for crashes; With intel Core i5-2...
6bf4c7c 2017-02-13 01:57:14 K.Ohta [UI][Qt] Update to track before commiting.
ba4f434 2017-02-12 17:57:46 K.Ohta [Qt][BUILD] Fix some FTBFSs.
ee24cca 2017-02-12 17:56:11 K.Ohta [VM][AY-3-891X] Fix pre-scaler (this is hidden feature?) ...
025e0ea 2017-02-12 17:54:40 K.Ohta [Win32][OpenGL] TRY: Fixing crash with OpenGL3.0 at Corei...


Name Rev. Zeit Autor Nachricht
master 7a70a00 2017-02-18 01:12:48 K.Ohta [DOC] Update Issues.See htt...


** 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