What exactly are the changes you had to make in the rockspec? Can you
attach your modified version here? I'll then try to use it to make a
version that works on both platforms.
On Dec 20, 2013 7:04 PM, "Eric Chiesse" <echie...@gmail.com> wrote:
> Hisham, I just saw the merge has been accepted. I'm glad it helped.
>
> I'd like just to remember there's another issue regarding the library
> naming difference between unix and windows ('pq' shall be specified on unix
> while 'libpq' must be used on windows).
>
> I couldn't examine this issue but I'd like to remember that it still
> occurs. Today, I need to edit the rockspec by hand in order to install the
> lib.
>
> Thank you
>
> Regards.
>
> ---
> Eric
>
>
> 2013/11/30 Eric Chiesse <echie...@gmail.com>
>
>> Hisham, I sent a pull request in GitHub regarding this subject.
>>
>> Regarding the path issue: Yes the name of the lib in Windows is
>> libpq.dll. I saw the patterns in cfg.lua but there might be something in
>> between that is not working. Unfortunately I didn't have time to explore
>> this problem in depth.
>>
>> ---
>> Eric
>>
>>
>> 2013/11/11 Hisham <h...@hisham.hm>
>>
>>> On 10 November 2013 21:26, Eric Chiesse <echie...@gmail.com> wrote:
>>> >
>>> > Hi all,
>>> >
>>> > I've been having trouble installing luasql-postgres on Windows (Vista)
>>> due to a list of problems. The first 2 were related to luasql project:
>>> > 1 - Compilation error due to non-standard syntax
>>> > 2 - Rockspec depending on "pq" doesn't work on windows where "libpq"
>>> must be specified.
>>> >
>>> > Problem number 2 can be a shared problem (between luasql and LR)
>>> because I don't know if it is possible to indicate different names for a
>>> dependency based on the OS flavor.
>>> >
>>> > Now comes the LR problem.
>>> > I solved the problems described above locally and it was possible to
>>> build luasql-postgres. But then occured the runtime error:
>>> > 3 - "R6034. An application has made an attempt to load the C runtime
>>> library incorrectly. ..."
>>> >
>>> > After some research, I found that this error occurs due to the lack of
>>> a manifest which is necessary when a dll is linked against MSVCRT.lib
>>> (linker /MD option).
>>> > LR creates a command for embedding the manifest in the resulting dll
>>> (in "src/luarocks/build/builtin.lua") but it was not working for
>>> luasql-postgres because the final output is not a single dll but a dll
>>> inside a directory (luasql/postgres).
>>> > I also solved problem number 3 locally and now I'm able to use the
>>> luasql-postgres.
>>> >
>>> > I have 2 questions:
>>> > 1 - How can I send my modifications to be applied to LR?
>>>
>>> You can send a pull request on Github at
>>> https://github.com/keplerproject/luarocks or just send a patch here at
>>> the mailing list, whatever is more convenient to you (on our end, the
>>> pull request is preferred of course since it's less work to
>>> integrate.)
>>>
>>> > 2 - Related to problem number 2. How to deal with the differences in
>>> library search conventions in different OSs?
>>>
>>> LR should already be handling that, that's odd... take a look at
>>> external_deps_patterns (in `src/luarocks/cfg.lua`). On Windows,
>>> there's both "?.dll" and "lib?.dll" there... is the library file
>>> called libpq.lib, by any chance?
>>>
>>> Thanks,
>>>
>>> -- Hisham
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> November Webinars for C, C++, Fortran Developers
>>> Accelerate application performance with scalable programming models.
>>> Explore
>>> techniques for threading, error checking, porting, and tuning. Get the
>>> most
>>> from the latest Intel processors and coprocessors. See abstracts and
>>> register
>>>
>>> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Luarocks-developers mailing list
>>> Luarocks-developers@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/luarocks-developers
>>>
>>
>>
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Luarocks-developers mailing list
> Luarocks-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/luarocks-developers
>
>
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Luarocks-developers mailing list
Luarocks-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/luarocks-developers
