1.24.0 1.25.0 pre : problem with build ? (1 Viewer)
- Thread starter framug
- Start date
Ukraine
- Thread starter
- Moderator
- #52
Hello,
Checking MFC give more results.
Now, all seems to be OK in logs but I only have TVengine in release folder
Checking MFC give more results.
Now, all seems to be OK in logs but I only have TVengine in release folder
- Moderator
- #53
and in VS ? what he say ?Now, all seems to be OK in logs but I only have TVengine in release folder
- Thread starter
- Moderator
- #54
Since the begining, I never had problem to compil all with VS (except dshow, not needed), even without DX9 SDK.
This thread has been made to show how could be problem for some devs wanted to collaborate in MP.
Now, it really drive me nuts that, it's not possible to do the entire process until the end (I mean without specific tool existing in IRC).
Then, it's up to you, if you want to fix that for others.
I'm ready to help but, finally, for me, it doesn't make difference...
This thread has been made to show how could be problem for some devs wanted to collaborate in MP.
Now, it really drive me nuts that, it's not possible to do the entire process until the end (I mean without specific tool existing in IRC).
Then, it's up to you, if you want to fix that for others.
I'm ready to help but, finally, for me, it doesn't make difference...
- Thread starter
- Moderator
- #55
The problem has been fixed.
With the help of azzuro (THX ), we found where was the problem.
Even if it's possible to compile DXSHOW filters with Java 13.2 (and maybe Java 14, who know ?), the entire compile of MediaPortal is only possible with Java 8 (old parameter 5 instead of 7 in .bat/scripts).
Then for the moment, you have to install the only Java 8 available on Oracle website ==> jdk-8u251-windows-i586.
Of course, the JAVA_HOME system parameter value need to be C:\Program Files (x86)\Java\jdk1.8.0_251
It can't be as simple as it is, hem...
With the help of azzuro (THX
), we found where was the problem.Even if it's possible to compile DXSHOW filters with Java 13.2 (and maybe Java 14, who know ?), the entire compile of MediaPortal is only possible with Java 8 (old parameter 5 instead of 7 in .bat/scripts).
Then for the moment, you have to install the only Java 8 available on Oracle website ==> jdk-8u251-windows-i586.
Of course, the JAVA_HOME system parameter value need to be C:\Program Files (x86)\Java\jdk1.8.0_251
It can't be as simple as it is, hem...
- Moderator
- #56
Hey @framug
you see, than you don't follow wiki instruction right ?
anyway, we must work on wiki for this, and hope fix problem with nuget.
for now we have :
you see, than you don't follow wiki instruction right ?
anyway, we must work on wiki for this, and hope fix problem with nuget.
for now we have :
- vsyasm provided as nuget (no need to touch anything) -> Done
- libbluray as nuget, but will be only bdj stuff for MP1 (so, no need apache ant, java to build MP) -> WIP
- DX9 SDK, but must be try on people who never setup Dx9 SDK on system. -> Done
- Thread starter
- Moderator
- #57
Hello,
Ah, nice !
Let's say mistakes were shared.
Be carefull with java 8.251 instead of 8.151, some warnings says that options will be depreciated in the future...
Good if Java, Ant, etc install not needed anymore.
What about submodule update for libbluray ? (init, sync, update)
What abbout Windows SDK (wich is 8.1, not 7.1 like wiki says).
Finally, if possible wiki to be reworked a bit for that (I know, it's big work), it would be nice.
Some proposal : remove all VS2013, all depreciated (YASM,...) it will be more clear.
My VS2015 give me V14 folder, not V12.
Try to put all in same place (I remember dev explanation in 1.16 wich is not in dev place)...
Git or Git for windows, since updates doesn't show the same screenshots when installing...
And finally, I suppose that no many people will go until the end, NSIS, etc..
Because you need a powerful computer for that.
Even with a little "war machine", it takes some minutes, faster is a .bat with net stop/start/tvservice and copy files for local deployment.
Ah, nice !
Let's say mistakes were shared.
Be carefull with java 8.251 instead of 8.151, some warnings says that options will be depreciated in the future...
Good if Java, Ant, etc install not needed anymore.
What about submodule update for libbluray ? (init, sync, update)
What abbout Windows SDK (wich is 8.1, not 7.1 like wiki says).
Finally, if possible wiki to be reworked a bit for that (I know, it's big work), it would be nice.
Some proposal : remove all VS2013, all depreciated (YASM,...) it will be more clear.
My VS2015 give me V14 folder, not V12.
Try to put all in same place (I remember dev explanation in 1.16 wich is not in dev place)...
Git or Git for windows, since updates doesn't show the same screenshots when installing...
And finally, I suppose that no many people will go until the end, NSIS, etc..
Because you need a powerful computer for that.
Even with a little "war machine", it takes some minutes, faster is a .bat with net stop/start/tvservice and copy files for local deployment.
Last edited:
- Moderator
- #58
it will be needed if you want update / build Bdj part of libbluray, but for MP itself not needed ( 99% of people)
libbluray must stay as is, because BDreader use files from him.
i don't know if we always use 7.1. need to be investigate.
Yasm is not deprecated, needed but maybe need to done section on wiki
Main MP
- Directshow Filter (mean libbluray on C part) - but library can be provided as nuget package (DX9 SDK / VSYASM) - need to keep how install this if user want to use it's own version or files.
- Client
- TVengine
3rd Part (what it can provided as nuget package)
- Libbluray (bdj part > JAVA8 / ANT)
i think we can't reducing more ....
when all my task are done, and merged to master, we can start to port it to VS2019, but this is not my part, too many issue in C/C++
if @tourettes can be here for help on this, MPAudioRenderer is one with error.
- Thread starter
- Moderator
- #59
And in a same way, if possible to go with NSIS 3.05 instead of NSIS 2.46...
- Moderator
- #60
If my memory serves me, need to redo all the NSIS scripts, because in version 3, either the format or the syntax has changed, I do not remember.And in a same way, if possible to go with NSIS 3.05 instead of NSIS 2.46...
--
WBR, ajs