PureBasic 5.73 | SpiderBasic 2.30 | Windows 10 Pro (x64) | Linux Mint 20.1 (x64)
Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.
You use one config for both tailbite, and i have 2 entries in both ide with the
same name (different shortcut)
Next problem (or the same), tailbite will use the x86 dir
Only way to test is to uninstall one of tailbite version, but i am lazy and
will wait for a update
greetings
thomas
PureBasic 5.73 | SpiderBasic 2.30 | Windows 10 Pro (x64) | Linux Mint 20.1 (x64)
Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.
TailBite does not support 2 running IDE´s. It tries to determine the current IDE (registry settings) and loads the prefs of this version.
The X64 config will be named TailBite_430_X64.prefs.
> It tries to determine the current IDE (registry settings)
Okay, the registry is allways x86
Is there one tailbite version for both?
PureBasic 5.73 | SpiderBasic 2.30 | Windows 10 Pro (x64) | Linux Mint 20.1 (x64)
Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.
ts-soft wrote:Is there one tailbite version for both?
Yes. You can copy TailBite into the PureBasic dir and a modified "TailBite.prefs" too. If TailBite is now started it loads the prefs from its current directory.
Hope that helps
Klaus
PS: Integer is currently not supported by LibraryMaker.exe and so is the /COMPRESSED flag
> Yes. You can copy TailBite into the PureBasic dir and a modified "TailBite.prefs" too. If TailBite is now started it loads the prefs from its current directory.
good idea, i will test it
PureBasic 5.73 | SpiderBasic 2.30 | Windows 10 Pro (x64) | Linux Mint 20.1 (x64)
Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.
> PS: Integer is currently not supported by LibraryMaker.exe and so is the /COMPRESSED flag
Just continue using "Long" also for x64. Since the parameter types are promoted to register size anyway, it makes no difference.
The /COMPRESSED flag does not work on x64, thats true. Just remove it.
freak wrote:Just continue using "Long" also for x64. Since the parameter types are promoted to register size anyway, it makes no difference.
The /COMPRESSED flag does not work on x64, thats true. Just remove it.
[41] DEC 9th 2008 TailBite V1.3 PR 1.879
- fixed RET X + 4 in X64 not needed
- fixed TailBite Warning: Unknown Windows API function (found by mistrel)
- fixed BuildApiList() was causing an invalid memory access error on Peeks()
- fixed FAsm error : reserved keyword used as symbol (found by lexvictory)
- fixed X64 FAsm error : invalid argument ... aligngosub (found by lexvictory)
- fixed tempdir was not cleaned while it was in use
- fixed symbol was removed when named the same as the procedure
- fixed do not extrn symbol that is already public
- fixed endfunctions for X64
[42] FEB 8th 2009 TailBite V1.3 PR 1.880
- fixed polib.exe not found if 'Don´t build library. only source files' was checked (found by lexvictory)
- fixed import libs where not written to objfiles.txt if 'Don´t build library. only source files' was checked (found by lexvictory)
- added /EXE option to stop pbcompiler running the exe after commented asm output 28.1.2009 2:55 (by lexvictory)
- added lexvictory´s multilib code that makes UNICODE/THREADSAFE/UNICODE+THREADSAFE in one library file
- fixed another extrn bug that has to be commented out (found by mback2k)
- fixed TBUpdater was broken
See first post for more details.
[Edit]The updater was broken. Users having an older version should not use the Check for updates Button[/Edit]
format MS COFF
macro pb_public symbol
{
public _#symbol
public symbol
_#symbol:
symbol:
}
Public me_PB_DataSection
Public me_s_s
Public me_PB_BSSSection
Public me_PB_DataPointer
Public me_l_home
Public me_PB_DataSectionStart
Public me_SYS_EndDataSection
Extrn me_HOME_RELEASE ; <- has to be added by hand !
section '.data' data readable writeable
macro pb_align Value { rb (Value-1) - ($-me_PB_DataSection + Value-1) mod Value }
me_PB_DataSection:
dd -1
dd 0
db 0
align 4
align 4
me_s_s:
dd 0
dd -1
align 4
section '.bss' readable writeable
macro pb_bssalign Value { rb (Value-1) - ($-me_PB_BSSSection + Value-1) mod Value }
me_PB_BSSSection:
align 4
me_PB_DataPointer rd 1
align 4
align 4
align 4
align 4
section '.data' data readable writeable
me_l_home:
me_PB_DataSectionStart:
dd me_HOME_RELEASE
me_SYS_EndDataSection: