Re: GM - more questions
10bxjfhf <[email protected]> Thu, 20 Feb 2020 20:09:00 -0800
| Newsgroups | gmane.comp.video.graphicsmagick.apis |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============2261698256816823857==
Content-Type: multipart/alternative;
boundary="------------FE8310E0B4674629CCB7CD15"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------FE8310E0B4674629CCB7CD15
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
On 2020-02-20 3:44 p.m., Bob Friesenhahn wrote:
> On Thu, 20 Feb 2020, 10bxjfhf wrote:
>> I had expected some output as well, but have not been able to find any.
>> As I am not building & using a command line utility, all of my debug
>> output is being redirected to a log text window, but I see nothing
>> from the GM code other than the exception which I eventually decoded
>> and spit out.
>
> If it is actually using code from the release, then there could be a
> problem due to varying Visual Studio versions. Try editing the
> installed log.mgk to change the default destination.
After looking at all of the log.mgk file I found, it looks like the only
thing these specify is the log file naming format. Nothing I could find
about where this file might end up(presumably close to the project root
or some temp directory) but I could not find a trace of any such named
files anywhere on the PC
>
> Prior to 1.3.34 the logs were sent to the Windows application log by
> default.
>
> We use the free Inno Setup installer
> (https://www.jrsoftware.org/isinfo.php) and the installer scripts are
> under VisualMagick/installer. For example, if you have the Inno Setup
> installer installed, then you can use it to open and "compile"
> gm-win32-Q8-dll.iss (or gm-win64-Q16-dll.iss) to create the same
> installation package that I do. Please note that some run-time DLLs
> from Visual Studio 2008 are copied into the installer. These DLLs
> will be of no value to Visual Studio 2019 but are needed by code built
> by Visual Studio 2008.
Good; I have used the Inno installer software for some of my own
projects, but feel I am way to far away in my understanding of what I am
doing here from actually building an installer
Right now I am still fighting with MSVC 2019 and its refusal to compile
the sub-projects unless the naming is 'acceptable'.
I have meanwhile deciphered the GM file naming convention to
differentiate between release and debug code, but the convention used
makes it almost impossible to implement it with MSVC 2019 macros and it
will/would mean to either revert to an much earlier IDE or finding a
workable scheme and reworking all sub-projects to satisfy MSVC 2019.
Right now it complains:
Description:
"D:\pkg\wx\MSVC2019\_3.1.2_2019\wxIC-MT\DebUniStat\IM_MOD_DB_TIFF_.dll:
The specified module could not be found.
", Reason: Unable to load module,
Module:
D:\Download\Graphics\graphicsmagick-code-c031--3ded\magick\module.c
function: OpenModule, Line: 1412
Even though I am sure that dll exists and is readable in the location it
says it is looking.
Then of course, there is the choice of either using magick or magick++
A lot to chew on
Arnold
--------------FE8310E0B4674629CCB7CD15
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 2020-02-20 3:44 p.m., Bob
Friesenhahn wrote:<br>
</div>
<blockquote type="cite"
cite="mid:[email protected]">On
Thu, 20 Feb 2020, 10bxjfhf wrote:
<br>
<blockquote type="cite">I had expected some output as well, but
have not been able to find any.
<br>
As I am not building & using a command line utility, all of
my debug output is being redirected to a log text window, but I
see nothing from the GM code other than the exception which I
eventually decoded and spit out.
<br>
</blockquote>
<br>
If it is actually using code from the release, then there could be
a problem due to varying Visual Studio versions. Try editing the
installed log.mgk to change the default destination.
<br>
</blockquote>
After looking at all of the log.mgk file I found, it looks like the
only thing these specify is the log file naming format. Nothing I
could find about where this file might end up(presumably close to
the project root or some temp directory) but I could not find a
trace of any such named files anywhere on the PC<br>
<blockquote type="cite"
cite="mid:[email protected]">
<br>
Prior to 1.3.34 the logs were sent to the Windows application log
by default.
<br>
<br>
We use the free Inno Setup installer
(<a class="moz-txt-link-freetext" href="https://www.jrsoftware.org/isinfo.php">https://www.jrsoftware.org/isinfo.php</a>) and the installer scripts
are under VisualMagick/installer. For example, if you have the
Inno Setup installer installed, then you can use it to open and
"compile" gm-win32-Q8-dll.iss (or gm-win64-Q16-dll.iss) to create
the same installation package that I do. Please note that some
run-time DLLs from Visual Studio 2008 are copied into the
installer. These DLLs will be of no value to Visual Studio 2019
but are needed by code built by Visual Studio 2008.
<br>
</blockquote>
Good; I have used the Inno installer software for some of my own
projects, but feel I am way to far away in my understanding of what
I am doing here from actually building an installer<br>
<p><br>
</p>
<p>Right now I am still fighting with MSVC 2019 and its refusal to
compile the sub-projects unless the naming is 'acceptable'.</p>
<p>I have meanwhile deciphered the GM file naming convention to
differentiate between release and debug code, but the convention
used makes it almost impossible to implement it with MSVC 2019
macros and it will/would mean to either revert to an much earlier
IDE or finding a workable scheme and reworking all sub-projects to
satisfy MSVC 2019.</p>
<p>Right now it complains:</p>
<p class="western" style="margin-bottom: 0cm"><font face="Source
Code Pro, serif"><font style="font-size: 9pt" size="2">Description:
"D:\pkg\wx\MSVC2019\_3.1.2_2019\wxIC-MT\DebUniStat\IM_MOD_DB_TIFF_.dll:
The specified module could not be found.</font></font></p>
<p class="western" style="margin-bottom: 0cm"><font face="Source
Code Pro, serif"><font style="font-size: 9pt" size="2">",
Reason: Unable to load module, </font></font>
</p>
<p class="western" style="margin-bottom: 0cm"> <font face="Source
Code Pro, serif"><font style="font-size: 9pt" size="2">Module:
D:\Download\Graphics\graphicsmagick-code-c031--3ded\magick\module.c
function: OpenModule, Line: 1412</font></font></p>
<p>Even though I am sure that dll exists and is readable in the
location it says it is looking. <br>
</p>
<p>Then of course, there is the choice of either using magick or
magick++</p>
<p>A lot to chew on</p>
<p>Arnold<br>
</p>
</body>
</html>
--------------FE8310E0B4674629CCB7CD15--
--===============2261698256816823857==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--===============2261698256816823857==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Graphicsmagick-apis mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/graphicsmagick-apis
--===============2261698256816823857==--