Tailbite --> Lib
Tailbite --> Lib
Just wondering if TailBite will be able to create .LIB files for version 4?
Be neat if it can create .LIB files!
Be neat if it can create .LIB files!
@}--`--,-- A rose by any other name ..
Use this for TailBite: Arguments = "%FILE" /KEEPSRCFILES /WRITEBATCH
TailBite creates *.lib
you find the lib in "Library sources"
TailBite creates *.lib
you find the lib in "Library sources"
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.

Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.

- NoahPhense
- Addict

- Posts: 1999
- Joined: Thu Oct 16, 2003 8:30 pm
- Location: North Florida
TailBite < = 1.3 not compatible with PB 4
but there is no new feature for this to integrate in "Tailbite 4"
but there is no new feature for this to integrate in "Tailbite 4"
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.

Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.

- NoahPhense
- Addict

- Posts: 1999
- Joined: Thu Oct 16, 2003 8:30 pm
- Location: North Florida
tailbite creates allways a lib file (normally deleted after creation), but with
"TailBite 4" and PB 4, we can use the lib file with Import
"TailBite 4" and PB 4, we can use the lib file with Import
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.

Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.

- NoahPhense
- Addict

- Posts: 1999
- Joined: Thu Oct 16, 2003 8:30 pm
- Location: North Florida
Hi ts-soft,
Thanks for the info. Can you humour me and tell me if I have this right (when tailbite is V4-able):
1: We create a Pure-Lib as always.
2: We also get a .LIB file.
3: ? We stick the Pure-Lib and .LIB into a folder of our own choice ?
4: We compile using Import, so Pure uses this to reference the Pure-Lib
5: PureBasic grabs the desire routines and builds into our exes
or:
3: We still stick the Pure-Lib (and now the .LIB) into userlibraries?
Either way (or any other) it is a great way to document dependencies!
Thanks for the info. Can you humour me and tell me if I have this right (when tailbite is V4-able):
1: We create a Pure-Lib as always.
2: We also get a .LIB file.
3: ? We stick the Pure-Lib and .LIB into a folder of our own choice ?
4: We compile using Import, so Pure uses this to reference the Pure-Lib
5: PureBasic grabs the desire routines and builds into our exes
or:
3: We still stick the Pure-Lib (and now the .LIB) into userlibraries?
Either way (or any other) it is a great way to document dependencies!
@}--`--,-- A rose by any other name ..
- NoahPhense
- Addict

- Posts: 1999
- Joined: Thu Oct 16, 2003 8:30 pm
- Location: North Florida
Is there currently no way to create our own userlibraries.
Other than C?
I just want to be able to store my own full libs in my Subsystem(s) ..
So that when I'm coding, I can be utilizing my libraries.
In the past, the only way I have been able to even create my own libs
is to use TailBite.
I don't want to carry around dll's.. unless of course, it is a DLL that I am
selling..
- np
Other than C?
I just want to be able to store my own full libs in my Subsystem(s) ..
So that when I'm coding, I can be utilizing my libraries.
In the past, the only way I have been able to even create my own libs
is to use TailBite.
I don't want to carry around dll's.. unless of course, it is a DLL that I am
selling..
- np
Sorry, for my english
@Dare2
we can use the userlib AND/OR the lib

This RCDATA.lib can be used by Import, but in this time is not compatible with PB 4 or test it!
@Dare2
we can use the userlib AND/OR the lib
TailBite create in "Library sources", for Example:ts-soft wrote:Use this for TailBite: Arguments = "%FILE" /KEEPSRCFILES /WRITEBATCH
TailBite creates *.lib
you find the lib in "Library sources"

This RCDATA.lib can be used by Import, but in this time is not compatible with PB 4 or 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.

Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.

ts-soft,
Thank you!
As proof of concept:
Did this: (Using 3.94)
TailBite it, using the manager and "Keep Source Files" checked.
Went to userlibraries, deleted the userlibrary it created. So no pure lib anywhere.
Went to My 3.94 folder\TailBite\Library sources\testTailBiteLib.lib
Copied the .LIB to a version 4.00 playpen area.
Did this (Using 4.00 Beta1)
JackPot.
Now it used no Pure libraries, really, so I minimised the chances of it jacking up .. and there are some bits there that I need to think through like the @nn .. and this is not version 4 compatible for a lot of things ... but .....
JACKPOT!
Wooo Hoooo!
Thanks again ts-soft and El_Choni!
Man oh man, I am jumping around like a maniac. This is so good.
In version 4, userlibs should be imported or else! Under pain of death - or worse - free updates removed! Just to document the fact they are used, if nothing else.
Thank you!
As proof of concept:
Did this: (Using 3.94)
Code: Select all
ProcedureDLL AttachProcess(Instance)
EndProcedure
ProcedureDLL DetachProcess(Instance)
EndProcedure
ProcedureDLL m2(v.l)
ProcedureReturn v * 2
EndProcedure
ProcedureDLL dV(v.l, m.l)
ProcedureReturn v / m
EndProcedureWent to userlibraries, deleted the userlibrary it created. So no pure lib anywhere.
Went to My 3.94 folder\TailBite\Library sources\testTailBiteLib.lib
Copied the .LIB to a version 4.00 playpen area.
Did this (Using 4.00 Beta1)
Code: Select all
Import "C:\code\PureBasic_4\TestImport\testTailBiteLib.lib"
Mul2(v.l) As "PB_m2"
DivVal(a.l,b.l) AS "PB_dV"
EndImport
Debug Mul2(2)
Debug DivVal(9,3)
Debug DivVal(2,6)Now it used no Pure libraries, really, so I minimised the chances of it jacking up .. and there are some bits there that I need to think through like the @nn .. and this is not version 4 compatible for a lot of things ... but .....
JACKPOT!
Wooo Hoooo!
Thanks again ts-soft and El_Choni!
Man oh man, I am jumping around like a maniac. This is so good.
In version 4, userlibs should be imported or else! Under pain of death - or worse - free updates removed! Just to document the fact they are used, if nothing else.
@}--`--,-- A rose by any other name ..
I have installed the userlib PBOSL_LoadDllMemory (it's written in c)
by createing you find the lib like: "PBOSL_LOADDLLMEMORY.lib"
I have importet this lib with Import at same time userlib installt (only
changed names). It runs without problems
by createing you find the lib like: "PBOSL_LOADDLLMEMORY.lib"
I have importet this lib with Import at same time userlib installt (only
changed names). It runs without problems
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.

Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.

No it's the sameShannara wrote:Okay .. it is safe to assume there are no advantages of a "lib" file over a purelib file?
When your UserLib use an other Userlib isn't good
You can import the Lib from other Userlib, in your Lib, no problems!
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.

Old bugs good, new bugs bad! Updates are evil: might fix old bugs and introduce no new ones.


