Welcome, Guest
Username: Password: Remember me
General discussions, feature requests for CodeTyphon Project and discussions that don't fit in any of the other specific CodeTyphon forum categories.

TOPIC:

CodeTyphon 4.00 GEN IV 11 years 9 months ago #3216

  • Arioch
  • Arioch's Avatar
  • Offline
  • Junior Member
  • Junior Member
  • Posts: 59
  • Thank you received: 1
@engerex i fixed install.bat for 3.10 to be able to install from anywhere to anywhere two weeks ago

do you want to make fixed install.bat for 4.00 ?

I'm feeling too lazy to do it again :-)

Please Log in or Create an account to join the conversation.

CodeTyphon 4.00 GEN IV 11 years 9 months ago #3220

  • Sternas Stefanos
  • Sternas Stefanos's Avatar Topic Author
  • Offline
  • Moderator
  • Moderator
  • Ex Pilot, M.Sc, Ph.D
  • Posts: 4535
  • Thank you received: 1114

engerex wrote:

sternas wrote: Please remove ALL links and files from old CT
and then install the new version 4.0

The new ver 4.0 CT has CTCenter for win32 to:

C:\codetyphon\binCenter\i386-win32-win32\CodeTyphon.exe


I found the problem.
Setup.bat > line 157

_____________________________________________________________
rem @@@@@@@@@@@@@@@@@@@@ Run CodeTyphon @@@@@@@@@@@@@@@@@@@@@
:GO_1


START binCenter\%varzipdir%\win32\CodeTyphon.exe

GOTO GO_END
_____________________________________________________________


replace with:

rem @@@@@@@@@@@@@@@@@@@@ Run CodeTyphon @@@@@@@@@@@@@@@@@@@@@
:GO_1

START binCenter\%varzipdir%-win32\CodeTyphon.exe

GOTO GO_END
PilotLogic Architect and Core Programmer

Please Log in or Create an account to join the conversation.

CodeTyphon 4.00 GEN IV 11 years 9 months ago #3225

  • opc0de
  • opc0de's Avatar
  • Offline
  • New Member
  • New Member
  • Posts: 15
  • Thank you received: 1
It compiles fine...

The IDE crashes when I try to use ORCA components, the Indy Issue witch I reported has not yet been fixed...

I don't find any improvment from 3.1 it should have been called 3.3 or somethin'

Thanks for the effort tough I am waiting for the next release maybe some stability will be the priority.

Please Log in or Create an account to join the conversation.

CodeTyphon 4.00 GEN IV 11 years 9 months ago #3228

  • gorkamorka
  • gorkamorka's Avatar
  • Offline
  • New Member
  • New Member
  • Posts: 18
  • Thank you received: 2
Congratulations.compiling and building the bigide worked fine.
Orca works for me.
Win7 64 Home Basic English .Lazarus BigIde 32

Please Log in or Create an account to join the conversation.

CodeTyphon 4.00 GEN IV 11 years 9 months ago #3229

  • Arioch
  • Arioch's Avatar
  • Offline
  • Junior Member
  • Junior Member
  • Posts: 59
  • Thank you received: 1
would it still compile if u do clean install, then run CT Center as 2nd menu and from the Center would build BigIDE Win64

would BigIDE Win32 be able to build after that ?
The following user(s) said Thank You: gorkamorka

Please Log in or Create an account to join the conversation.

CodeTyphon 4.00 GEN IV 11 years 9 months ago #3240

  • gorkamorka
  • gorkamorka's Avatar
  • Offline
  • New Member
  • New Member
  • Posts: 18
  • Thank you received: 2
I will try and report it here

Please Log in or Create an account to join the conversation.

CodeTyphon 4.00 GEN IV 11 years 9 months ago #3241

  • Juhasz Robert
  • Juhasz Robert's Avatar
  • Offline
  • New Member
  • New Member
  • Posts: 7
  • Thank you received: 0
I have an interesting problem, which is working in 3.10 perfectly:

Fatal error:
openal.pas(77,1) Fatal: Syntax error, "identifier" expected but "TYPE" found

Whats wrong?

unit openal;

{$IFDEF FPC}
// Added by bero
{$MODE Delphi}
{$IFDEF CPUI386}
{$DEFINE CPU386}
{$ASMMODE INTEL}
{$ENDIF}
{$IFNDEF WIN32}
{$LINKLIB c}
{$ENDIF}
{$ENDIF}

interface

uses
Classes
, SysUtils
{$IFDEF Win32},Windows{$ENDIF}
;

{ $ DEFINE ALUT} //define ALUT to use alut.dll


const
{$IFDEF Win32}
callibname='OpenAL32.dll';
calutlibname='Alut.dll';
{$ENDIF}
{$IFDEF Linux}
callibname='libopenal.so';
calutlibname='libalut.so';
{$ENDIF}


type
// OpenAL boolean type.
TALboolean = Boolean;
PALboolean = ^TALboolean;
//character
TALchar = char;
PALchar = pchar;
// OpenAL 8bit signed byte.
TALbyte = ShortInt;
PALbyte = ^TALbyte;
// OpenAL 8bit unsigned byte.
TALuByte = Char;
PALuByte = PChar;
// OpenAL 16bit signed short integer type.

Please Log in or Create an account to join the conversation.

CodeTyphon 4.00 GEN IV 11 years 9 months ago #3242

  • Arioch
  • Arioch's Avatar
  • Offline
  • Junior Member
  • Junior Member
  • Posts: 59
  • Thank you received: 1
what is line #77 ? is it

type // OpenAL boolean type.

?

If so - that means that neither "Win32" nor "Linux" were defined.

What is your environment ?

Please Log in or Create an account to join the conversation.

CodeTyphon 4.00 GEN IV 11 years 9 months ago #3244

  • gorkamorka
  • gorkamorka's Avatar
  • Offline
  • New Member
  • New Member
  • Posts: 18
  • Thank you received: 2
Hello Arioch,

Here is what i did;

I had a BigIde 32 installation on my win7 64 system with no problems.I build BigIde 64 with succes but Orca 3D samples compiles and runs with a white screen ( nothing draws to screen ,only white color on 3D scene window.2D samples works fine) )

I deleted c:\codetypon for a fresh install..First i build BigIDe 64 and second BigIde 32 withoud errors and can use both withoud crashing the Ide.

I noticed the buildd procces takes very long time..looked to the output of build command i saw the script first builds the small ide and then builds the big ide.

I have switchable graphics card.i tried not working ORCA 3D samples with both onboart Intel and External ATI cards an have the same results.Dxdiag says I have DX 11 installed.

Note: I give Orca 64 bit report only for infomation to CT Team, but i dont ask them to fix this issue..I am happy with 32 bit and 32 bit apps works fine on most 64 bit systems.It is not a big problem for me..The only thing that i wish from CT Team(and Lazarus component/unit writers) is more document.Without document we cannot use and know the abilities of packages/components and can't use them ).Freepascal,Lazarus and CT developers gives this tools for free to us.They dont ask to pay and spent time ( stolen from the loved once )on the projects.I think we must only report some ıssues and dont trying force to fix them.( i speak this words not to you Arioch please dont missunderstood me.Only general))

Please Log in or Create an account to join the conversation.

Last edit: by gorkamorka.

CodeTyphon 4.00 GEN IV 11 years 9 months ago #3245

  • Sternas Stefanos
  • Sternas Stefanos's Avatar Topic Author
  • Offline
  • Moderator
  • Moderator
  • Ex Pilot, M.Sc, Ph.D
  • Posts: 4535
  • Thank you received: 1114
Thanks Sir
ORCA 3D don't work at Win64 yet.
ORCA 2D work OK (Win 32/64, Linux 32/64 and FreeBSD 32/64)

Our first priority is to make ORCA 3D for Win64, we prepare ORCA with OpenGL API for this

The only DirectX 3D library can work on Win64 is pl_AsphyreSphinx,
look at CodeOcean Samples after enabled DirectX 11 API.

and we want your help...

for your problem, please show us the line 77
PilotLogic Architect and Core Programmer

Please Log in or Create an account to join the conversation.

Last edit: by Sternas Stefanos.

CodeTyphon 4.00 GEN IV 11 years 9 months ago #3247

  • gorkamorka
  • gorkamorka's Avatar
  • Offline
  • New Member
  • New Member
  • Posts: 18
  • Thank you received: 2
Hello Mr. Sternas,

On my Win7 64 bit environment Orca2D and Orca3D works when i compile samples with BigIde32 as 32 bit application.32 Bit compiled Orca3D apps runs smooth on 64 Bit system..With BigIde64 only Orca2D works.

Regards.

Please Log in or Create an account to join the conversation.

CodeTyphon 4.00 GEN IV 11 years 9 months ago #3249

  • Juhasz Robert
  • Juhasz Robert's Avatar
  • Offline
  • New Member
  • New Member
  • Posts: 7
  • Thank you received: 0
win7 64bit
and the type line the 77.


Tried to change:

{$IFDEF Win64}
callibname='OpenAL32.dll';
calutlibname='Alut.dll';
{$ENDIF}
{$IFDEF Win32}
callibname='OpenAL32.dll';
calutlibname='Alut.dll';
{$ENDIF}
{$IFDEF Linux}
callibname='libopenal.so';
calutlibname='libalut.so';
{$ENDIF}

and its working.

Please Log in or Create an account to join the conversation.

Last edit: by Juhasz Robert.

CodeTyphon 4.00 GEN IV 11 years 9 months ago #3250

  • Arioch
  • Arioch's Avatar
  • Offline
  • Junior Member
  • Junior Member
  • Posts: 59
  • Thank you received: 1
repeating again - what is the line 77, what is it??? quote it and few lines above and below?

Please Log in or Create an account to join the conversation.

CodeTyphon 4.00 GEN IV 11 years 9 months ago #3251

  • Arioch
  • Arioch's Avatar
  • Offline
  • Junior Member
  • Junior Member
  • Posts: 59
  • Thank you received: 1
is FPC 32-bit or 64-bit ?

is MSWINDOWS defined or not ?

Please Log in or Create an account to join the conversation.

CodeTyphon 4.00 GEN IV 11 years 9 months ago #3252

  • Juhasz Robert
  • Juhasz Robert's Avatar
  • Offline
  • New Member
  • New Member
  • Posts: 7
  • Thank you received: 0
With {$IFDEF MSWINDOWS} line against the {$IFDEF Win32}, working with 64bit and 32bit compiler.

The line 77 is the type line.

const
{$IFDEF Win32}
callibname='OpenAL32.dll';
calutlibname='Alut.dll';
{$ENDIF}
{$IFDEF Linux}
callibname='libopenal.so';
calutlibname='libalut.so';
{$ENDIF}


77: type
// OpenAL boolean type.
TALboolean = Boolean;
PALboolean = ^TALboolean;
//character
TALchar = char;
PALchar = pchar;
// OpenAL 8bit signed byte.
TALbyte = ShortInt;
PALbyte = ^TALbyte;
// OpenAL 8bit unsigned byte.
TALuByte = Char;
PALuByte = PChar;
// OpenAL 16bit signed short integer type.

Please Log in or Create an account to join the conversation.

CodeTyphon 4.00 GEN IV 11 years 9 months ago #3253

  • Sternas Stefanos
  • Sternas Stefanos's Avatar Topic Author
  • Offline
  • Moderator
  • Moderator
  • Ex Pilot, M.Sc, Ph.D
  • Posts: 4535
  • Thank you received: 1114
Your problem is that for
win64 old code NOT "define" anything
Try this:

const
{$IFDEF WINDOWS} // for Win32+Win64+WinCE or
{$IFDEF MSWINDOWS} // for Win32+Win64
callibname='OpenAL32.dll';
calutlibname='Alut.dll';
{$ENDIF}

{$IFDEF Linux} or
{$IFDEF UNIX}
callibname='libopenal.so';
calutlibname='libalut.so';
{$ENDIF}


77: type
// OpenAL boolean type.
TALboolean = Boolean;
PALboolean = ^TALboolean;
//character
TALchar = char;
PALchar = pchar;
// OpenAL 8bit signed byte.
TALbyte = ShortInt;
PALbyte = ^TALbyte;
// OpenAL 8bit unsigned byte.
TALuByte = Char;
PALuByte = PChar;
// OpenAL 16bit signed short integer type.
PilotLogic Architect and Core Programmer

Please Log in or Create an account to join the conversation.

Last edit: by Sternas Stefanos.

CodeTyphon 4.00 GEN IV 11 years 9 months ago #3254

  • Arioch
  • Arioch's Avatar
  • Offline
  • Junior Member
  • Junior Member
  • Posts: 59
  • Thank you received: 1
is the FPC only targeted compiler for that unit ?

i think some of the suggested changes would not work in vanilla Delphi

Please Log in or Create an account to join the conversation.

CodeTyphon 4.00 GEN IV 11 years 9 months ago #3255

  • Sternas Stefanos
  • Sternas Stefanos's Avatar Topic Author
  • Offline
  • Moderator
  • Moderator
  • Ex Pilot, M.Sc, Ph.D
  • Posts: 4535
  • Thank you received: 1114
Sir, we don't care about Delphi here... :kiss:
PilotLogic Architect and Core Programmer

Please Log in or Create an account to join the conversation.

Last edit: by Sternas Stefanos.

CodeTyphon 4.00 GEN IV 11 years 9 months ago #3261

  • Dibo
  • Dibo's Avatar
  • Offline
  • Junior Member
  • Junior Member
  • Posts: 37
  • Thank you received: 1
Hi,

I just updated CT from 3.10 to 4.0 (clean installation) and I'm confused how to create cross elements now. In 3.10 I had full lists of all elements but now it is very short, no windows targets (I'm running CT on Linux Mint 14 64 bit, XFCE Edition). So I looked to the refreshed help about CT Studio. Tried download new targets, but after refresh, my list is still short (se attached screen). And output (translated from Polish):

[INFO]: CodeTyphon Download Engine settings
1
www.pilotlogic.com/codetyphon/toolchains/zzctdirver.ctv
x86_64-linux
zzctdirver.ctv
xxxx5
xxxx6


[INFO]: Download file, please wait..
sudo: missing tty and unknown password program
sudo: missing tty and unknown password program
/usr/lib/codetyphon/ScriptsLin/ln_xCodeTyphon_UDownload.sh: line 28: cd: zdownload: No such file or directory
sudo: missing tty and unknown password program
sudo: missing tty and unknown password program
sudo: missing tty and unknown password program
_______________________________________________________________

Terminate Action at 11-2-13 15:00:21
Total time: 00:00:00.108
ExitCode : 0

Same with building target:


GNU Cross toolschains Engine settings

lin64
x86_64-linux
xxxx
i386
win32
xxxx
i386-win32

=====================================================================
BinUtils Build for i386-win32
=====================================================================
.
sudo: missing tty and unknown password program
sudo: missing tty and unknown password program
sudo: missing tty and unknown password program
sudo: missing tty and unknown password program
sudo: missing tty and unknown password program
sudo: missing tty and unknown password program
/usr/lib/codetyphon/ScriptsLin/ln_Cross_Binutils.sh: line 50: cd: /usr/lib/codetyphon/CrossEng/binutils: No such file or directory
/usr/lib/codetyphon/ScriptsLin/ln_Cross_Binutils.sh: line 56: ./configure: No such file or directory
sudo: missing tty and unknown password program
sudo: missing tty and unknown password program

??????????????????????????????????????????????????????????????????????
[ERROR]: Sorry, Toolschains for i386-win32 NOT Build...
??????????????????????????????????????????????????????????????????????
_______________________________________________________________

Terminate Action at 11-2-13 15:04:34
Total time: 00:00:00.114
ExitCode : 0


Attachments:

Please Log in or Create an account to join the conversation.

CodeTyphon 4.00 GEN IV 11 years 9 months ago #3266

  • Arioch
  • Arioch's Avatar
  • Offline
  • Junior Member
  • Junior Member
  • Posts: 59
  • Thank you received: 1
For core functionality - sure.
But libraries are not that clear.

For example RxLib is officially dead, so you can fork it and enhance w/o concern for Delphi, true.

However, speaking of libs like JCL and TDbf, which i had been contributor too, they could only be Delphi-ignorant if you forked them and cut any ties with upstream (RxLib is dead thus having no upstream thus nothgin to loose here).

Sorry, but i just didn't know which kind of livbs the aforementioned Orca was :-)

Please Log in or Create an account to join the conversation.