NO

Author Topic: TLIDE  (Read 4369 times)

Offline TimoVJL

  • Global Moderator
  • Member
  • *****
  • Posts: 2091
TLIDE
« on: January 30, 2017, 05:12:58 PM »
 TLIDE Tiny Lousy IDE :)

Minimal IDE for testing one file code with different compilers, not for seriuos work ;)
I made it for small testing purposes.

If local TLIDE.ini exists, it is used, otherwise ini-file from current user document folder is used.
Options dialog option Local force saving to local ini-file.

TLIDE.ini
[path]
ccpath= current compiler path and options
path= current path for compiler PATH , optional
include= current include path for INCLUDE

[link]
link_path= current linker, optional
link_opt= current options for linker

[path64] for second options
[link]

[options]
check_only=1 check only insert -Zs to compiler commandline

Code: [Select]
[path]
ccpath=hjwasm64.exe -coff
ccpath1=hjwasm64.exe
ccpath2=hjwasm64.exe -coff
path=c:\code\HJWasm
path1=c:\code\HJWasm
include=

[link]
link_path=c:\code\PellesC8\bin\polink.exe
link_path1=c:\code\PellesC8\bin\polink.exe
link_opt=-subsystem:windows
link_opt1=-subsystem:windows -libpath:c:\code\PellesC8\lib\Win
link_opt2=-subsystem:console -libpath:c:\code\PellesC8\lib

[options]
check_only=1
[Font1]
FaceName=Lucida Console
Size=12
[Font2]
FaceName=Lucida Console
Size=12

EDIT: TLIDE_a2.zip Now Build -> Local options... creates empty ini-file, if it doesn't exists.
EDIT: TLIDE_a3.zip Accelerator keys and Execute open cmd.exe if runs without target file.

EDIT: TLIDE_WS_a7.zip fix use thread for executing exe and compiler
« Last Edit: April 29, 2017, 02:39:04 PM by TimoVJL »
May the source be with you

Offline jj2007

  • Member
  • *
  • Posts: 536
Re: TLIDE
« Reply #1 on: January 31, 2017, 10:16:51 AM »
Not lousy at all, Timo! I have a plugin for my IDE that does very similar things, so I know how useful that can be...

Offline frankie

  • Global Moderator
  • Member
  • *****
  • Posts: 2096
Re: TLIDE
« Reply #2 on: January 31, 2017, 05:15:07 PM »
Nice job Timo  :)
Please to allow use of fSDK in compilation change in RunCcDlg.c the line:
Code: [Select]
#define WIN32_LEAN_AND_MEAN
#include <windows.h>
#include <commctrl.h>
#include <shfolder.h>
With:
Code: [Select]
#define WIN32_LEAN_AND_MEAN
#include <windows.h>
#include <commctrl.h>
#ifndef __FSDK__                //If using standard PellesC headers
#include <shfolder.h>           //Use shfolder
#else
#include <ShlObj.h>             //For fSDK use shlObj.h
#endif
;)
« Last Edit: January 31, 2017, 05:17:47 PM by frankie »
It is better to be hated for what you are than to be loved for what you are not. - Andre Gide

Offline TimoVJL

  • Global Moderator
  • Member
  • *****
  • Posts: 2091
Re: TLIDE
« Reply #3 on: January 31, 2017, 05:40:45 PM »
OK. That shfolder.h is deprecated, so in next version it is removed totally, replaced with
Code: [Select]
HRESULT WINAPI SHGetFolderPathA(HWND, int, HANDLE, DWORD, LPSTR);
HRESULT WINAPI SHGetFolderPathW(HWND, int, HANDLE, DWORD, LPWSTR);
#ifdef UNICODE
#define SHGetFolderPath  SHGetFolderPathW
#else
#define SHGetFolderPath  SHGetFolderPathA
#endif
#define CSIDL_PERSONAL  0x0005
May the source be with you

Offline Vortex

  • Member
  • *
  • Posts: 797
    • http://www.vortex.masmcode.com
Re: TLIDE
« Reply #4 on: February 01, 2017, 08:50:06 PM »
I agree with Jochen. Not lousy at all. Keep up the nice work Timo.
Code it... That's all...

Jokaste

  • Guest
Re: TLIDE
« Reply #5 on: October 28, 2017, 05:18:03 PM »
Thanks Timo I was looking for such a tool since a long Time.
I use it now.


When you make post you always have 2 files : _a*.zip and _WS_*.zip what does it mean?

Offline TimoVJL

  • Global Moderator
  • Member
  • *****
  • Posts: 2091
Re: TLIDE
« Reply #6 on: October 28, 2017, 05:36:14 PM »
WS is for workspace and a* for for alpha versions.
May the source be with you